Hi Kamal, what about refreshing the user's session and/or the tokens that are associated with the session? It is difficult to find concrete information for how long the session lasts, I found that even if the inner X-MS-CLIENT-PRINCIPAL's expiry claim has passed the session is still active and no reauthentication is needed. For AppService authentication middleware (which as I understood is similar to container app authentication middleware) there are /.auth/refresh and /.auth/me which refresh access tokens and return access tokens associated with user. I would like to extend the user's session for as long as possible so to prevent a reauthentication.
have you got the easy auth working with the container app behind the application gateway where the URL clients hit your container app isn't the same as your container app and you have to use custom domains for your container app?
Hi Kamal, what about refreshing the user's session and/or the tokens that are associated with the session? It is difficult to find concrete information for how long the session lasts, I found that even if the inner X-MS-CLIENT-PRINCIPAL's expiry claim has passed the session is still active and no reauthentication is needed.
For AppService authentication middleware (which as I understood is similar to container app authentication middleware) there are /.auth/refresh and /.auth/me which refresh access tokens and return access tokens associated with user.
I would like to extend the user's session for as long as possible so to prevent a reauthentication.
love you man, great video!
good job, thank you
have you got the easy auth working with the container app behind the application gateway where the URL clients hit your container app isn't the same as your container app and you have to use custom domains for your container app?
same here