Configuring OAuth Support

Configuring the Oracle Communications Unified Session Manager for OAuth support consists of:

• Creating one or more OAuth profiles
• Applying each profile globally or to sip-interfaces

To configure an OAuth profile:

1. From superuser mode, use the following command sequence to access http-config element and define your profile.

   ORACLE# configure terminal
   ORACLE(configure)# session-router
   ORACLE(session-router)# http-config
   ORACLE(http-config)# sel

2. Name your profile for reference within your configuration.
3. You can set the host parameter to an FQDN or an ip address. If you use an FQDN, the Oracle Communications Unified Session Manager resolves it to an ip address when the configuration is loaded.
4. The num-connections parameter specifies the number of connections to be setup with the STS server. The Oracle Communications Unified Session Manager establishes this number of connections when it boots or when the configuration is activated.
5. The max-outstanding-msgs parameter specifies the maximum number of outstanding messages per connection. An outstanding message is a request from the Oracle Communications Unified Session Manager that has not had a response. When reaching this threshold, the Oracle Communications Unified Session Manager stops sending requests on the connection until the number of outstanding messages falls back below this maximum. If the max-outstanding-msgs parameter is set to 1, the Oracle Communications Unified Session Manager waits for a response before sending another request on a connection.
6. The Oracle Communications Unified Session Manager uses the port parameter differently depending on whether the host parameter is configured as an IP address or an FQDN. If the host parameter is an FQDN name, the Oracle Communications Unified Session Manager performs a lookup at a DNS server. In this case, you may or may not configure a port. If you configure the port parameter, the Oracle Communications Unified Session Manager uses the configured port ignoring any port specified in the record returned by the DNS server. If you do not configure the port parameter, the Oracle Communications Unified Session Manager uses the port returned by the DNS server. If the host parameter is set to an ip-address, you must configure the port parameter and the Oracle Communications Unified Session Manager always uses the port parameter’s value.