Is your feature request related to a problem? Please describe.
Apple Silicon Local Credentials state: Only one Apple silicon authentication method is allowed at a time. If you specify multiple authentication methods then only one will be saved via the priority order as follows; local end user's password, then an existing local account, then the local super service account, Jamf Pro API client/secret credentials, and finally Jamf Pro API username/password credentials.
As such, a situation where using the Jamf Pro API, plus AuthMDMFailoverToUser OR AuthCredentialFailoverToUser results in the user being required to enter their password any time the failover kicks in. super supports the key AuthAskUserToSavePassword which saves the user's credentials to the keychain, but if used in conjunction with the Jamf Pro API, this key will result in super preferring to default to prompt the user for their password and not attempting to make use of the Jamf Pro API.
Describe the solution you'd like.
Although clearly stated the order of preference for authentication and the fact that super will only save on authentication type, this FR is requesting the ability to save multiple cached credentials in order to facilitate the following flow: Jamf Pro API attempt > Failover to User > Save User Credentials for future failovers.
Could you describe alternatives you've considered?
None in practice. Reviewed manage_authentication_options() in the super script which is where the script is checking/making use of the saved credentials.
Additional Context:
Feature request submitted on behalf of user:Poppy - MacAdmins Slack
Is your feature request related to a problem? Please describe.
Apple Silicon Local Credentials state: Only one Apple silicon authentication method is allowed at a time. If you specify multiple authentication methods then only one will be saved via the priority order as follows; local end user's password, then an existing local account, then the local super service account, Jamf Pro API client/secret credentials, and finally Jamf Pro API username/password credentials.
As such, a situation where using the Jamf Pro API, plus
AuthMDMFailoverToUserORAuthCredentialFailoverToUserresults in the user being required to enter their password any time the failover kicks in.supersupports the keyAuthAskUserToSavePasswordwhich saves the user's credentials to the keychain, but if used in conjunction with the Jamf Pro API, this key will result insuperpreferring to default to prompt the user for their password and not attempting to make use of the Jamf Pro API.Describe the solution you'd like.
Although clearly stated the order of preference for authentication and the fact that
superwill only save on authentication type, this FR is requesting the ability to save multiple cached credentials in order to facilitate the following flow: Jamf Pro API attempt > Failover to User > Save User Credentials for future failovers.Could you describe alternatives you've considered?
None in practice. Reviewed
manage_authentication_options()in thesuperscript which is where the script is checking/making use of the saved credentials.Additional Context:
Feature request submitted on behalf of user:Poppy - MacAdmins Slack