You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default NanoMDM will save the client identity certificate for a device enrollment during the Authenticate check-in message (for both the file and mysql backends). However if enrollments happened in such a way that client certificates were missed (say, via migration) then we should support a way to "recapture" client certificates in storage by saving the identity certificate. It would be wasteful to do this on every request so perhaps it would be only be turned on with a flag.
The text was updated successfully, but these errors were encountered:
As a potential workaround one can simply re-send the enrollment profile (via the MDM channel) to re-enroll with a client which will capture a new Authenticate message.
By default NanoMDM will save the client identity certificate for a device enrollment during the Authenticate check-in message (for both the
file
andmysql
backends). However if enrollments happened in such a way that client certificates were missed (say, via migration) then we should support a way to "recapture" client certificates in storage by saving the identity certificate. It would be wasteful to do this on every request so perhaps it would be only be turned on with a flag.The text was updated successfully, but these errors were encountered: