To prevent unexpected Google consent prompts during each user login with Jamf Connect, you must modify the existing Jamf Connect login window configuration profile.
Requirements
Access to your Jamf Connect configuration profile
Access to your Google identity provider (IdP) administrator console
An existing Jamf Connect configuration with Google as the IdP
- Log in to your Google Cloud Console.
- Navigate to .
- Select the Jamf Connect app in the OAuth 2.0 Client IDs section.
- In the Authorized redirect URIs section, change the existing URL value to https://[orgdomain]/jamfconnect.
You must register and authenticate ownership of all URIs included in this section. Failure to register and authenticate will result in the following error: "Access blocked: This app's request is invalid".
Best Practice:The orgdomain URL is a placeholder domain that requires you to change the existing placeholder information to your organization's domain prior to completing the configuration. Jamf recommends only using a domain that your organization has control over.
- Click Save.
- Open the Jamf Connect Configuration app or your Jamf Connect login window configuration profile PLIST file.
- Locate the Redirect URI (
OIDCRedirectURI) setting. - Change the default value of
https://127.0.0.1/jamfconnect to https://example.com/jamfconnect. - Save and deploy your Jamf Connect configuration profile.
Google consent prompts no longer appear for users during each login attempt with Jamf Connect.