Skip to main content
Question

Self Service not remembering credentials

  • February 12, 2018
  • 6 replies
  • 30 views

Forum|alt.badge.img+9

I've noticed lately that the Mac OS Self Service is not remembering our credentials when we have the Remember Me box checked. Is anyone else seeing this?

6 replies

Forum|alt.badge.img+17
  • Contributor
  • February 12, 2018

Hi @luke.reagor ,

This is a known issue that we have filed as PI-005230.

Please check future Release Notes for information as to whether PI-005230 has been fixed in that particular release.

If you would like to open a case and have it attached to PI-005230, please contact Support either by giving us a call, sending an e-mail to support@jamf.com, or using the Support section of Jamf Nation.

Thanks!
Were Wulff
Jamf Customer Experience


Forum|alt.badge.img+17
  • Contributor
  • February 13, 2018

@luke.reagor

Just to update you, this was fixed with the 10.2.0 release.

It didn't make it into the Release Notes, but I checked with the team that worked on the fix and they verified that it was fixed in 10.2.0.

Once you update your JSS to version 10.2.0, the passwords should save when the Remember Me box is checked in Self Service.

Thanks!
Were Wulff
Jamf Customer Experience


Forum|alt.badge.img+1
  • New Contributor
  • February 14, 2019

Sorry to dig this old thread up, but it seems like the error is back. We are on 10.9.0 in the jamf-cloud. The error can be reproduced on all our systems. An entry in the keychain is successfully created, but it's not loaded / used when self service is opened again.


ThijsX
Forum|alt.badge.img+20
  • Employee
  • February 14, 2019

Same here.. for all our systems Jamf Pro 10.9.0-t1544463445 on-prem and all our clients run latest binary.
edit; created case JAMF-0639446


Forum|alt.badge.img+8
  • Contributor
  • February 27, 2019

Doesn't look like it was acknowledged in the 10.10 release notes. @txhaflaire have you had any updates on your case?


ThijsX
Forum|alt.badge.img+20
  • Employee
  • February 27, 2019

Hi @krispayne

In my support case they told me it will be fixed in the 10.10 patch, last week we patched our Jamf Pro environment to 10.10 and i can confirm this issue is resolved. Tested on multiple clients.

Cheers.