Identity Cloud Service Provider
Overview
The Oracle Network Management System Operations Mobile App and Flex Operations support login using the Oracle Identity Cloud Service (IDCS). IDCS requires the same configuration as the LDAP/AD user validation in the CentricityServer.properties file described in the Using LDAP/AD User Validation section.
Identity Cloud Service – Setup
You will need to define two Applications in the Identity Cloud Service:
1. OMA Authentication Application
Define an Application for the OMA client to authenticate against.
Allowed Grant types should include Authorization Code and Implicit
Allow Non-HTTPS URLs checked
Redirect URL should be the deployed OMA OAuth callback page for the customer environment. OMA provides mobile/OMA2/src/oauth-callback.html as an example callback page. Deploy or adapt that callback page, set its targetOrigin value to the exact OMA application origin, and register the deployed callback page URL with IDCS as the redirect URL.
This application will be used to configure the OMA Client in the src/js/resources/config/loginSettings.js file. Supply customer/environment-specific values through customer/project configuration:
self.IDCS_HOST = 'REPLACE-ME-IDCS-HOST';
self.IDCS_REDIRECT_URL = 'REPLACE-ME-IDCS-REDIRECT-URL'; // wherever oauth-callback.html is deployed
self.IDCS_CLIENT_ID = 'REPLACE-ME-IDCS-CLIENT-ID';
2. NMS Authentication Application
Define an Application for the NMS WLS to use to authenticate credentials via the IDCS Integration Provider. This Application will contain both a Client ID and a Client Secret.
The Client Configuration will have the Register Client Checked
Allowed Grant Types will include (Resource Owner, Client Credentials, SAML2 Assertion, Refresh Token, Authorization Code, Implicit)
Allow non-HTTPS URLs checked
Redirector URL to an existing URL (for example, https://google.com)
Client Type: Confidential
Authorized Resources: Specific
Resources/Add Scope: NMSWLS/OMATest
Grant the Client Access to the Identity Cloud Service APIs (Cloud Gate, Application Administrator, Me, User Administrator).
Resources will include:
• Registered Resources selected
• Access Token Expiration set to 604800
• Primary Audience set to the OMA Application Name.
3. Define Users and Groups
Users and Groups can be defined in IDCS directly or by configuring IDCS to connect to another authentication provider to get the user credentials and group membership. If using IDCS to define the users and groups, define the users and groups using the same group requirements as configured for the LDAP/AD in the CentricityServer.properties file.
4. Admin Session Duration
In the IDCS admin console, go to Settings/Session/Session Settings/Session Duration and set it to 604800
URL with IDCS Login Script
For OMA to receive the IDCS OAuth authorization response, deploy or adapt the callback page provided at mobile/OMA2/src/oauth-callback.html. The callback page reads the OAuth response from the redirect URL, sends a structured oauth_callback message back to the OMA opener window, and closes the popup when possible.
In the deployed callback page, set targetOrigin to the exact OMA application origin, including protocol, host, and port. Do not leave targetOrigin as a wildcard. Register the deployed callback page URL with IDCS as the redirect URL, and use that same URL as IDCS_REDIRECT_URL in the OMA client configuration.
NMS WebLogic Managed Server – IDCS Integration Provider
In the NMS WebLogic Managed Server, add the Oracle Identity Cloud Integrator Authentication Provider to your security realm:
1. Open Edit Tree.
2. Open Security, and then select Realms, myrealm, and Authentication Providers, in that order.
3. Select New.
4. Give the authentication provider a name (for example, IDCS) and select Oracle Identity Cloud Integrator for Type.
5. On the Common tab, set Control Flag to Optional or Sufficient, depending on whether additional providers are to be processed after this provider.
6. Set Active Types to include idcs_user_assertion, Idcs_user_assertion, and Authorization.
7. On the Oracle Identity Cloud Integrator Parameters tab, set the provider-specific values as follows:
Host: identity.oraclecloud.com (the base name of the IDCS server https://idcstrial09.identity.oraclecloud.com, excluding the leftmost component, which is the hostname used below).
Port: 443
SSLEnabled: Selected
Tenant: idcstrial09 (the hostname from the IDCS cloud server https://idcstrial09.identity.oraclecloud.com).
Client Id: The hexadecimal string from the IDCS Application Configuration General Information section.
Client Secret: The hexadecimal string copied from the IDCS Application Configuration Information section.
Confirm Client Secret: The same value as Client Secret.
Client Tenant: Leave blank.
All other values can retain their defaults.
8. Save and commit the changes.
9. Open Security Data Tree.
10. Open Realms, and then select myrealm, Authorizers, XACMLAuthorizer, Domain, and Identity Assertion, in that order.
11. Select Add Condition.
12. Select Allow Access to Everyone from Predicate List.
13. Select OK and save the changes.
14. Open Edit Tree.
15. Open Environment, and then select Servers. Select your managed server in the list of servers.
16. Open the Advanced tab, and then select the Node Manager sub-tab.
17. Add the following to Arguments (single line):
-Dweblogic.security.SSL.hostnameVerifier=
weblogic.security.utils.SSLWLSWildcardHostnameVerifier
18. Save and commit the changes.
19. Restart the admin and NMS WebLogic managed servers.
Configure the OMA Client
The OMA Application will need to know about the IDCS configuration. Please set the src\js\resources\config\loginSettings.js file values to match the above IDCS configuration:
self.IDCS_HOST = 'REPLACE-ME-IDCS-HOST';
self.IDCS_REDIRECT_URL = 'REPLACE-ME-IDCS-REDIRECT-URL';
self.IDCS_CLIENT_ID = 'REPLACE-ME-IDCS-CLIENT-ID';