00:00:05:19 - 00:00:06:17
So what I want to do
00:00:06:17 - 00:00:09:17
is go through a few sample scenarios,
00:00:10:11 - 00:00:14:13
of increasing complexity, covering
various different bits of functionality
00:00:14:23 - 00:00:17:19
just to really drill home that basic
00:00:17:19 - 00:00:20:19
understanding
that we've we've tried to show there.
00:00:21:01 - 00:00:23:25
So the first one is understanding
primarily rules,
00:00:23:25 - 00:00:26:25
but then also a little
based on the weightings as well.
00:00:27:24 - 00:00:29:11
So the scenario that we've got here
00:00:29:11 - 00:00:33:02
and hopefully this little graphic makes
sense, is we've got a customer
00:00:33:14 - 00:00:36:24
was logging in to their account
on your particular storefront.
00:00:37:27 - 00:00:41:13
Now this storefront has various
different rules associated with it.
00:00:41:24 - 00:00:45:04
And what we want to do in these example
scenarios is investigate
00:00:45:04 - 00:00:48:17
if our customer is able to access
particular products.
00:00:51:05 - 00:00:54:02
So what we'll see on a lot of these
examples is we have a customer,
00:00:55:07 - 00:00:55:18
we have a
00:00:55:18 - 00:00:58:18
products, and we're assessing
whether they can access.
00:00:58:25 - 00:01:02:06
And then we'll get to a particular rule
and then we'll see how it proceeds
00:01:02:06 - 00:01:05:06
from that.
00:01:06:22 - 00:01:08:04
So our first example on the left
00:01:08:04 - 00:01:11:12
hand side here is with a scope.
00:01:11:12 - 00:01:14:12
And target is not related
to this particular customer.
00:01:15:11 - 00:01:19:22
So our customer that's logging in
is UK based and is a non administrator.
00:01:20:20 - 00:01:23:20
And what we'll see is if we've got a rule
which has
00:01:24:25 - 00:01:27:15
an administrator scope and
00:01:27:15 - 00:01:30:15
well relates to a just our product,
00:01:31:00 - 00:01:35:27
our administrator scope does not match
what that customer is involved in.
00:01:35:27 - 00:01:37:26
So our customer is not administrator.
00:01:37:26 - 00:01:41:03
So what that means
is that this rule just fails evaluation
00:01:41:15 - 00:01:43:23
and does not match
that particular customer.
00:01:43:23 - 00:01:46:23
So therefore this particular rule
doesn't apply in this scenario.
00:01:47:10 - 00:01:47:28
Easy as that.
00:01:51:22 - 00:01:53:28
On the flip side, on the on the right hand
side,
00:01:53:28 - 00:01:58:02
here is a rule
that does match the particular scenario.
00:01:58:18 - 00:02:02:24
So we've got a non administrator scope
and we've got our product.
00:02:03:06 - 00:02:05:26
The rule passes evaluation.
00:02:05:26 - 00:02:09:07
We decide then whether or not
we're giving or denying access
00:02:09:07 - 00:02:11:00
to that particular product.
00:02:11:00 - 00:02:14:13
In this case we are giving access
so the customer can view the product.
00:02:15:03 - 00:02:18:03
If we nice and easy.
00:02:20:18 - 00:02:22:08
The opposite is also true though,
00:02:22:08 - 00:02:26:01
so we can even if a rule passes evaluation
00:02:26:06 - 00:02:29:23
as we've seen, as we set that up,
we can still deny access.
00:02:29:23 - 00:02:32:23
It's not just immediate access granted.
00:02:32:24 - 00:02:38:02
So even if that customer and the product
combination rule passes evaluation,
00:02:38:09 - 00:02:41:09
we can still deny access to the product.
00:02:46:19 - 00:02:48:02
Now we have another scenario here,
00:02:48:02 - 00:02:51:28
which is where two rules are applying
to the same.
00:02:52:10 - 00:02:55:19
Customer and product combination.
00:02:56:01 - 00:02:59:28
So just a slight variation on the example
we saw earlier on.
00:03:00:17 - 00:03:03:18
So where a connection is subject
to multiple rules, evaluate
00:03:03:21 - 00:03:07:25
and will proceed for maximum to minimum
weighting of those rules.
00:03:08:20 - 00:03:11:28
So what we see here
we have a higher weighted rule
00:03:12:20 - 00:03:16:29
which passes evaluation
and grants access to the product.
00:03:18:12 - 00:03:20:23
We then have a lower weighted rule,
00:03:20:23 - 00:03:24:22
which still passes evaluation and denies
access to the product.
00:03:25:10 - 00:03:29:17
However, because the low because this rule
is lower weighted, it is ignored.
00:03:29:29 - 00:03:34:04
So what it essentially means is that
this customer will have access to that
00:03:34:04 - 00:03:37:09
particular product,
regardless of the fact that this rule says
00:03:37:09 - 00:03:40:09
it shouldn't.
00:03:40:24 - 00:03:41:23
Hopefully that makes sense.
00:03:41:23 - 00:03:44:10
So let me just go into my
00:03:44:10 - 00:03:45:16
store front here.
00:03:45:16 - 00:03:48:16
I've got a lot of tabs open.
00:03:54:11 - 00:03:56:02
So this is that scenario unfolding.
00:03:56:02 - 00:03:58:19
And this is one of those store fronts
I've given you access to.
00:03:58:19 - 00:04:00:25
If you want to take a look
at this later on.
00:04:00:25 - 00:04:04:04
So I'm viewing the storefront
as that particular customer
00:04:04:04 - 00:04:09:01
now that we've been looking at,
and we can see that they are able to view
00:04:10:12 - 00:04:11:18
product four,
00:04:11:18 - 00:04:13:21
which is what we're expecting is
and this is the fourth product
00:04:13:21 - 00:04:15:28
we're working on,
and they are able to view it,
00:04:15:28 - 00:04:18:28
even though there's another rule
saying they shouldn't be able to view it.
00:04:25:23 - 00:04:28:02
And then the other scenario
we talked about where there is
00:04:28:02 - 00:04:31:25
equal rule weightings
are pointing to the same connection.
00:04:33:24 - 00:04:36:12
If they are all granting the same access,
00:04:36:12 - 00:04:39:23
then that will be adhered to,
that will be followed.
00:04:40:09 - 00:04:44:12
If they are providing conflicting access,
then it will deny access
00:04:44:12 - 00:04:47:12
to that particular product.
