Domains
Overview
A domain controls how a user is authorized. Once a user is authorized, domains can also auto-provision a user in USuM (including a default Service). If a user is not auto-provisioned, the user must have been provisioned by API into USuM before they are assigned a Service on the network.
Each user goes through a single domain authorization process upon log in. There can be multiple domains configured each having different kind of authorization. A user's domain is determined by Location. If a user does not match any of the Domains, they are considered to be part of the Domain marked as 'default'.
CPS supports the following types of authorizations per domain:
-
USuM Authorization
-
Allow All Users
-
Anonymous Authorization
-
USuM Validation Only
-
Proxy AAA Authorization
-
One-click Voucher Authorization
A domain can also auto provision a subscriber in SPR and associate a default service to it. This provides an option to register the subscriber based on Primary Credential and Password received from the incoming request, for example, Radius Username and Radius Password. This method is generally used in scenarios where the system is configured to “auto-learn” subscribers and assign a default service profile.
When multiple domains are configured it can be very difficult to select a single domain to authorize/authenticate a subscriber. This problem can be overcome by configuring the Locations on the individual domains. Location provides an option to select the individual domain based on the attributes received from the incoming request like Framed-IP, NAS-IP or based on AVP with the combination of Time Zone.
Domain provides multiple advanced options which help us to take some default actions based on the conditions. Advanced rules determine if unknown subscribers can come into the system and defines the unknown service. This is often used if subscribers self-provision and so are initially unknown or a default service can be assigned to a known subscribers.
General Tab
The General tab determines the type of authentication for that domain. As explained earlier, there are multiple types of authorization methods that can be used:
- USuM Authorization
- Allow All Users
- Anonymous Authorization
- USuM Validation Only
- One-click Voucher Authorization
USuM Authorization
This authorization method authenticates the subscriber based on the field selected at User Id Field and Password Field.
Note | The Remote Db Lookup Key Field is used in the Geo-Redundant deployments whenever we need to look up a profile across multiple sites. |
There are many fields available for both User Id Field and Password Field; user can select the appropriate authorization object from the drop-down list as shown below depending on the requirement.
Allow All Users
This authorization method allows all the requests without validating or authenticating the subscriber. This type of authentication usually is used for automatic provisioning of the subscriber.
Anonymous Authorization
Anonymous Authorization validates the value received in object selected for User Id Field and Password Field against the Anonymous User Name and Anonymous Password provided.
If the values match, CPS applies the services configured in Anonymous Subscriber Service in Advanced Rules tab.
With this authorization method, anonymous subscribers do not exist in SPR. This subscriber exists only in Policy Builder and all the validation of the incoming requests happens against the Anonymous User Name and Password provided in Policy Builder.
USuM Validation Only
This authorization method is similar to USuM Authorization.
One-click Voucher Authorization
This authorization method is used for authenticating the requests based on voucher.
One-click is an authorization method where users login and are redirected to a page where they click 'OK' or 'Agree' to be logged in and use the network. With an Anonymous Authorization, no limits on time or volumes are put in place. With a Voucher method, however, CPS can limit the session time or volume or quota time.
This validates user name and password in User Id Field and Password Field against the values configured in One Click User Id and One Click Password and on authentication user gets the service configured.
Provisioning Tab
The Provisioning tab defines whether auto provisioning of subscribers within the SPR should occur. This method is generally used in scenarios where the system is configured to “auto-learn” subscribers and assign a default service profile.
not-set
For subscribers who are already registered under USuM, generally no configuration is required on the Provisioning Tab.
Voucher Registration
Use this provisioning option with a domain that has an authorization configuration set to One-Click Voucher Authentication. This allows the provisioning of the voucher (subscriber) with a pre-configured service.
USuM Registration
In Auto Provisioning, CPS can support a list of custom Attribute Value Pair (AVP) as a key to the subscriber as shown below:
For example, the Authorization section or General Tab would be configured with Allow All Users and the Provisioning section would be configured to provision users with a key of the MSISDN as Primary Credential of subscriber.
A List of Available services in the System could also be provisioned with the subscriber as Autostart Services.
Copy Existing Registration
This configuration could be used when a copy of an already registered subscriber in Unified SuM is required with new account details and new information such as MAC Credentials (if Auto Register MAC Credential use case template used). One such example is “Access Code Use Case Scenario”.
Locations Tab
The Locations tab defines the rules used to guide the requests to a non-default domain. A location is determined by an attribute on a user's initial network login message.
If no locations are specified, the domain matches all users who do not match another domain.
Location Attribute could be any of the following:
-
AVP Value (Format code\value)
-
Framed IP Location Type
-
Generic Location Type
-
Nas IP and Framed IP Location Type
-
Nas IP Location Type
Note | By default, Framed IP Location Type is selected. |
Advanced Rules Tab
Domain provides multiple advanced options which help us to take some default actions based on the conditions. Advanced rules determine if unknown subscribers can come into the system and define the unknown service. This is often used if subscribers self-provision and so initially unknown or a default service can be assigned to known subscribers.
Service Provider Domains
A service provider exists inside a domain to customize the user experience for a subset of users (usually defined by a Service Provider) within a Domain. A Service Provider is determined by a user's realm (typically something like: @cisco.com).
For example, let's say we have a Domain for the Mall of America. All users get redirected to a portal where they can buy a voucher for service. However, The Mall of America has an agreement with Cisco to allow only Cisco customers free access. Cisco has set up a RADIUS AAA server to authenticate users. We can set up a domain which authorizes based on USuM and a Service Provider which matches the realm (“@cisco.com”) that authorizes the @cisco.com users against Cisco's RADIUS AAA server. If we want to minimize the amount of traffic to Cisco's server and improve the experience for the user, we could set up TAL to provision the users MAC or IP in USuM so after the first login they no longer need to provide their credentials.
A Service Provider domain can be created by clicking on the Service Provider link on the General tab under Actions and Create Child.
After creating a Service Provider, we need to select the type of authorization from the authorization drop-down list as shown below.
For example, here we can select Proxy AAA Authorization as explained in the above example for Cisco customers to be authenticated at Cisco’s AAA server. Hence CPS needs to proxy those requests to AAA server of Cisco.
And in the service provider settings we need to provide the realm information to match the Cisco customers as shown below.
This configuration authenticates the requests coming with realm cisco.com with Cisco AAA server using service provider domain cisco.com else by default, parent domain is used to authenticate the subscribers.
Create a Default Domain
This section describes an example configuration on how to create a domain. Depending on your network requirements, various parameters configured in a Domain can change.
At any time, there must be one domain defined in the system and that domain is assigned to a session if the location rules do not resolve to any domain. This domain specifies that when a request is received, the Unified SuM SPR profile is loaded using the Radius User Name. No provisioning is triggered, and no additional profile data is retrieved. All advanced options are set to default.
Create an Auto Provision Domain
The following steps create a domain for auto provisioning of subscribers.
Create a Domain - Location Based Selection
The domain created in these steps is selected based on the framed IP in the incoming request and then authentication is done based on the authorization type selected.