Updating mobile-config.xml
This is the second step in a two-step process to first update the WebSphere Trust Association Interceptor filter for OAuth, and then second, update the mobile-config.xml.
Procedure
- Follow the steps from Changing Mobile configuration property values to check-out the mobile-config.xml file for updates.
-
Using a text editor, edit the mobile-config.xml file and locate the following
section. Ensure that Security Settings have
enabled="true"
and that theAuthType
is set toOAuth
as shown above.<!-- SECURITY SETTINGS SECTION --> <SecuritySettings enabled="true"> <!-- Authentication mechanism for the server. One of TAM, SiteMinder, Form, Basic, SPNEGO, OAuth --> <AuthType>OAuth</AuthType>
-
Still editing the mobile-config.xml file, locate the end of the Security Settings section by
searching for
</SecuritySettings>
. If the following keys are not already listed in the file, insert them within the Security Settings section, just before the end of the section:<!-- OAuth Settings. The following settings are only applicable when AuthType is set to OAuth --> <!-- OAuthAuthorizationURL: Fully qualified URL of the OAuth Authorization server authorize endpoint. For example: https://oauthserver.example.com/op/authorize This field MUST be specified when using OAuth. --> <OAuthAuthorizationURL></OAuthAuthorizationURL> <!-- OAuthTokenURL: Fully qualified URL of the OAuth Authorization server token endpoint. For example: https://oauthserver.example.com/op/token This field MUST be specified when using OAuth. --> <OAuthTokenURL></OAuthTokenURL> <!-- OAuthClientId: OAuth Client ID used by the Connections Mobile Server application. You must ensure that this client id is registered with your OAuth Authorization Server. Some Authorization Servers may generate a new client id for each new application type, and if so, replace this value here with the one registered at the autorization server. --> <OAuthClientId>connections_social_mobile</OAuthClientId> <!-- OAuthScopes: If your OAuth Authorization server requires clients to use a custom scope, then entire the scope or scopes here that should be used by the Connections Mobile app. Separate multiple scopes using a space character. --> <OAuthScopes></OAuthScopes>
-
Find the Authorization URL for your OAuth 2.0 Authorization server and insert it as the value of
the
<OAuthAuthorizationURL>
tag. -
Find the Token URL for your OAuth 2.0 Authorization server and insert it as the value of the
<OAuthTokenURL>
tag. - Save mobile-config.xml and follow the steps for checking the file back into WebSphere Application Server.