question

BryanPowell-0839 avatar image
0 Votes"
BryanPowell-0839 asked saldana-msft edited

CMG: Moving to token based auth from HTTPS

Last summer like many organizations we deployed a CMG to allow work from home to be more seamless in terms of MECM management using client based certificates and HTTPS MPs. Since then we have upgraded to the point where the token based authentication is an option. Because it is inherently more simple than a full HTTTPS/client certificate setup, I am wondering what the process would be for migrating to token based auth.

If I am understanding what I am reading this process is fairly hands off and up to date clients will have already gotten the token essentially ready for use. This leads me to believe I can just flip the switch to http/https both being allowed and that is it. This seems dangerously simple though, so I wanted to check here to see if I am missing anything obvious. The docs do seem to indicate token based auth may be more for the purposes of provisioning non-typical clients, so perhaps I am off base.


mem-cm-generalmem-cm-site-deployment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jason-MSFT avatar image
1 Vote"
Jason-MSFT answered

I can't say I've tested this scenario explicitly, but this is all that it should take. I would remove the PKI-issued client auth certs from the clients as well to prevent any client selection conflict.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BryanPowell-0839 avatar image
0 Votes"
BryanPowell-0839 answered

Thanks. We will do some testing if we attempt this change, and if I have anything of note to report I will share it here.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.