PingID User Management
Feature
Integrating Germain with Ping for Authentication
Configuration in PingID
The configuration in PingID depends on your organization's setup. We can guide you through the process of configuring PingID for OAuth and OpenID authentication methods.
Configuration in Germain
Sign in to your Germain application as an administrator.
Go to System > System Settings > Root Config (Advanced).
Navigate to services > authentication. In AuthenticationConfig, set the following:
defaultRedirectPath: workspace URL (e.g.,
/germainapm/workspace/app
)
Go to System > Auth Settings > Authentication.
Click the Plus button to add a new Authentication Provider.
Select OAuth Provider and click next.
Configure the provider settings:
Provider Name: Name for your Auth Provider
Client ID: <Client ID Copied from PingID>
Client Secret: <Client Secret Copied from PingID> (or empty if using a public OAuth client - note this is not recommended, if Client ID is empty, PKCE is used by default)
Authorization Grant Type: authorization_code
Redirect URI Template:
{baseUrl}/login/oauth2/code/{registrationId}
Authorization URI:
https://<yourPingIDDomain>/fss/as/authorization.oauth2
Token URI:
https://<yourPingIDDomain>/fss/as/authorization.oauth2
User Info URI:
https://<yourPingIDDomain>/fss/idp/userinfo.openid
JWK Set URI:
https://<yourPingIDDomain>/fss/pf/JWKS
User Name Attribute: email
JWS Algorithm: (leave blank)
Role List Path: (leave blank)
Scope values: openid, profile, email, roles
Use PKCE: enable this to force using PKCE
Click Finish.
Restart the Tomcat services to apply the changes.
If you have any issues with logging in with your OAuth provider after restarting, you can enable
DEBUG
logging in the REST service for the following packagecom.germainsoftware.apm.auth.security
This will provide additional logging in the REST service log file (when a login attempt is made) to help troubleshoot any configuration issues.
Once completed, the login page should display the "Login with PingID" OAuth provider option.
Service: Authentication
Feature Availability: 2023.1 or later