Alpaca fails to get credentails from NoMAD/Keychain #32
Comments
segan5
pushed a commit
to segan5/alpaca
that referenced
this issue
Mar 6, 2020
…ry/Managed Preferences before reading them from ~/Library/Preferences
camh-
pushed a commit
that referenced
this issue
Mar 8, 2020
Read NoMAD configuration values from /Library/Managed Preferences before reading them from ~/Library/Preferences. In manual testing with split preferences, UseKeychain is now being read from Managed Preferences plist while UserPrincipal is still being read from the user's preferences plist. This will avoid users having to use that manual workaround on corporate managed devices that deploy a configuration profile to manage NoMAD. Fixes: #32 Co-authored-by: Seng Ern Gan <sengern.gan@anz.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even when NoMAD is installed and configured to use the system keychain, Alpaca fails to read the NoMAD configuration and get the credentials out of the keychain. It disables proxy authentication as a result:
When NoMAD app preferences are managed by a configuration profile which means they get written to
/Library/Managed Preferences/$USER/com.trusourcelabs.NoMAD.plist. When a user then logs into NoMAD, their particular details get written to/Users/$USER/Library/Preferences/com.trusourcelabs.NoMAD.plist. In this case,UseKeychaingets defined inManaged PreferencesandUserPrincipalgets defined in the user'sPreferencesdirectory.Alpaca uses the
defaultscommand to read the configuration, and it looks like this is only reading the plist file in the user'sPreferencesdirectory.A workaround is to manually use
defaults writeto setUseKeychainto1in the user's plist:The text was updated successfully, but these errors were encountered: