If the password is not known to them (in my case even as the admin even I don’t know their local Jamf password since I didn’t write it down after their account was created) then they can’t use anything but SSO.įor User-Initiated Enrollments and the Self Service I enabled SSO so they can use that there as well. This prevents not just access via the failover URL but also restricts them from using the Jamf API. Thanks for the info though the more sure fire way to ensure folks with Jamf web console access use SSO only is to not give them the password to their local Jamf account. If all goes well, access should be blocked. Once the change is made, you should be able to test by trying to log into the Jamf Pro server with an affected account using the ?failover login page. Remove that account’s ability to log in to the Jamf Pro server using the the ?failover login page.Prevent that account from being able to edit the Single Sign On settings in Settings: System Settings.
#Jamf saml update#
Uncheck the Update checkbox for the Jamf Pro Server Actions: Sso Settings.Go to Jamf Pro Server Settings and locate the Sso Settings checkboxes.Identify the user or group where you want to block their ability to login using the the failover URL.Go to Settings: System Settings: Jamf Pro User Accounts & Groups.
#Jamf saml how to#
If you want to block access to the failover login for a specific user or a group, here’s how to do this: For more details, please see below the jump. This URL is designed to let you bypass the SSO login page and take you to Jamf Pro’s own login, so that if your SSO provider is having a bad day, you can still log into your Jamf Pro server.įor those wanting to make sure that that their folks are only using SSO for logins, this can seem like a security hole. As part of Jamf Pro’s single-sign on (SSO) logins, there’s an option to bypass the SSO login using the following URL:
0 kommentar(er)
