Permissions issues after applying CIPP 2.13.... #1140
CentralizedServices
started this conversation in
General
Replies: 1 comment
-
UPDATE: Figured out the permissions issue... the tech who installed CIPP for us left a couple of months ago. I just found that there are THREE CIPP-SAM app registrations, so I was changing permissions on the wrong one! :( Anyway, that fixed the permissions check, all good. However an hour later I'm still not seeing the frontend 2.12 updating to 2.13 or 2.14. I just found the Discord for CyberDrain, so I'll post up in there. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We've had a solid-working CIPP for a couple of months now, and it updates normally with no issues. The other day I tried to update to 2.13 and had no problems with the update to the 2.3 backend, but the frontend won't update from 2.12. I went through the permissions check and I get the following:
Your refresh token matches key vault.
Your access token contains the MFA claim.
Your Secure Application Model is missing the following delegated permissions:
DeviceManagementManagedDevices.PrivilegedOperations.All
Policy.ReadWrite.ApplicationConfiguration
SharePointTenantSettings.ReadWrite.All
SecurityIncident.Read.All
SecurityIncident.ReadWrite.All
However, when I roll through the permissions with a fine-toothed comb, all of those delegated permissions match exactly what is shown on https://cipp.app/docs/user/gettingstarted/permissions/#delegated-permissions -- and the Application permissions match, as well. Examples:
I'm stuck... what are my next troubleshooting steps?
Beta Was this translation helpful? Give feedback.
All reactions