# SSO integration no longer honoring admin permissions
**URL:** https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871
**Category:** SSO
**Created:** [July 3, 2024, 9:09pm UTC](https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871 "2024-07-03T21:09:41Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@JesseB](https://meta.discourse.org/u/JesseB)
#### Post date: [July 3, 2024, 9:09pm UTC](https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871/1 "2024-07-03T21:09:41Z")
Hello,
I exclusively use the SSO integration on my Discourse platform. I noticed today that, when I sign in to my Admin account using SSO, I no longer see the Admin related menus, and the `/admin` endpoint does not work.
However, on another device I have, which has remained logged in for about a week, I _do_ see the Admin menu. This only seems to happen on fresh sign ins, which make me think that:
1. admin permissions are stored in the session itself (which would make sense)
2. the SSO integration is no longer properly adding in the admin permission when creating sessions
This means that, once my other device inevitably gets logged out, I’ll be stuck from accessing my admin menus.
I’ve confirmed with another admin on my forum, and the same happens to him if he signs in on an incognito tab.
I also used the “Impersonate” button on a test account earlier today, which is when I noticed this issue. I’m not sure if that would be related or not, but worth mentioning?
This now happens on all devices (Mac, PC, iPhone), as well as both admin accounts on my site, regardless of whether we clear cookies or not. We are both still listed on our `/about` endpoint as Admins, so we were not accidentally removed.
Hopefully this is easy to reproduce & resolve. If I can provide any more information, I’d be happy to do so.
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 3, 2024, 9:14pm UTC](https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871/2 "2024-07-03T21:14:52Z")
Hey @JesseB 👋 Welcome to Meta!
Do you have Cloudflare?
There is another recent [topic](https://meta.discourse.org/t/cant-find-upgrade-discourse-button-after-last-upgrade/314625/23?silent=true) where this prevented the admin from accessing the admin area.
> [@Resolving "SyntaxError: Unexpected identifier #..." caused by Cloudflare Auto Minify](https://meta.discourse.org/t/resolving-syntaxerror-unexpected-identifier-caused-by-cloudflare-auto-minify/311390):
>
> Cloudflare’s [‘Auto Minify’](https://developers.cloudflare.com/speed/optimization/content/auto-minify/) feature will break recent versions of Discourse. In the browser console, you will see an error like: Uncaught SyntaxError: Unexpected identifier '#...' Cloudflare are aware of the issue, and have added this message to their dashboard: Note: Please note that this feature may not be fully compatible with certain newer CSS and JS language features, which could potentially affect the functionality of the site Unfortunately, despite this critical issue, the feature wi…
---
### Author:  [@JesseB](https://meta.discourse.org/u/JesseB)
#### Post date: [July 3, 2024, 9:25pm UTC](https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871/3 "2024-07-03T21:25:53Z")
Major props for putting 2:2 together. I wouldn’t have assumed it was Cloudflare, especially given the fact that I just updated Discourse today — but that’s exactly it.
Thank you, issue resolved.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [August 2, 2024, 9:26pm UTC](https://meta.discourse.org/t/sso-integration-no-longer-honoring-admin-permissions/314871/4 "2024-08-02T21:26:37Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.