Previous Topic: Update the SSL VersionNext Topic: Proxy UI for the Secure Proxy Server


Update Oauth

If you have created copies of oauth.jsp, openid.jsp, or forms.jsp, the installer will not upgrade those copies. Some administrators use copies of oauth.jsp as Resource Filters for the realm to redirect to the launch url of the application. CA CloudMinder has changed the implementation of oauth.jsp, openid.jsp, and forms.jsp. Therefore, you cannot access the User Console when logging in with an authmethod if the corresponding CA SiteMinder realm uses a copy of these JSPs as a resource filter.

This problem can be solved in one of two ways:

Keeping the realms intact

If you support a tenant that is using Oauth, perform these steps on each Secure Proxy Server:

  1. Change to the redirectjsp directory:
    cd /opt/CA/secure-proxy/Tomcat/webapps/affwebservices/redirectjsp 
    
  2. Back up the existing App/Tenant specific oauth.jsp files. For example:
    mv oauth-google.jsp oauth-google.jsp.orig
    mv oauth-facebook.jsp oauth-facebook.jsp.orig
    
  3. Replace the App/Tenant oauth files with the new oauth.jsp file that came with upgrade.
    cp oauth.jsp oauth-google.jsp
    cp oauth.jsp oauth-facebook.jsp
    
  4. Update the oauth.jsp file.

    If your external and internal hostnames are different for your Secure Proxy Server system, edit the server.conf file on the Secure Proxy Server system. Change this file to list both the internal and external hostnames for redirects.

    1. Edit opt/CA/secure-proxy/proxy-engine/conf/server.conf
    2. Change the line which reads:
      redirectrewritablehostnames=<internal hostname>
      

      Replace this line with the following line:

      redirectrewritablehostnames=<internal hostname, external hostname>
      
  5. Restart the Secure Proxy Server as follows:
    service S98sps stop
    service S98sps startssl