Skip to main content
Solved

Unable to use Change password option in Jamf Connect Menu App


Forum|alt.badge.img+5
  • New Contributor
  • 2 replies

When trying to use Change password option within Jamf Connect Menu App, the following message comes up, Configuration file does not specify default realm. The realm is configured in the Configuration Policy for Jamf Connect, but it seems it's not able to read it.

Best answer by ilya25

Rocketman_Zac wrote:

Hello,

The Jamf Connect Log can be gathered to a file on the Desktop, and should be able to confirm whether Jamf Connect is reading the correct realm from the preference key:

 

log show --st:le compact --predicate 'subsystem == "com.jamf.connect"' --debug > ~/Desktop/JamfConnect.log

 

 Might also be worth creating a krb5.conf file as described in the solution here: https://community.jamf.com/t5/jamf-pro/kerberos-sso-default-realm-issue/m-p/236344/highlight/true#M224163

Hope this helps!



Thanks. Was able to figure it out by adjusting password complexity policy related to characters. 

View original
Did this topic help you find an answer to your question?

4 replies

ejadadic
Forum|alt.badge.img+9
  • Contributor
  • 28 replies
  • June 8, 2022

What Idp are you using?


Forum|alt.badge.img+5
  • Author
  • New Contributor
  • 2 replies
  • June 9, 2022
ejadadic wrote:

What Idp are you using?


on-prem


Forum|alt.badge.img+6

Hello,

The Jamf Connect Log can be gathered to a file on the Desktop, and should be able to confirm whether Jamf Connect is reading the correct realm from the preference key:

 

log show --st:le compact --predicate 'subsystem == "com.jamf.connect"' --debug > ~/Desktop/JamfConnect.log

 

 Might also be worth creating a krb5.conf file as described in the solution here: https://community.jamf.com/t5/jamf-pro/kerberos-sso-default-realm-issue/m-p/236344/highlight/true#M224163

Hope this helps!



Forum|alt.badge.img+5
  • Author
  • New Contributor
  • 2 replies
  • Answer
  • June 16, 2022
Rocketman_Zac wrote:

Hello,

The Jamf Connect Log can be gathered to a file on the Desktop, and should be able to confirm whether Jamf Connect is reading the correct realm from the preference key:

 

log show --st:le compact --predicate 'subsystem == "com.jamf.connect"' --debug > ~/Desktop/JamfConnect.log

 

 Might also be worth creating a krb5.conf file as described in the solution here: https://community.jamf.com/t5/jamf-pro/kerberos-sso-default-realm-issue/m-p/236344/highlight/true#M224163

Hope this helps!



Thanks. Was able to figure it out by adjusting password complexity policy related to characters. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings