So when you consent, it will only apply the consent to what is needed. And I think it being an app means that it has it's own built in connection strings, forgive me if I'm not understanding the question. I take it you setup a user account for the access assuming it needed an api key to do it. As far as I have seen, the SSO integrations don't require api keys or access. I've only recently started playing with SSO, but as far as I know and I could be very wrong here, but the token generated by the logon session carry's with it certain data that is passed to the requesting server via the users interaction. So there is do "direct" call from entra to meraki and vice versa. Everything is done via the browser session and the tokens contain the data that each need to cater for, and checks are done to ensure that the app requesting the access is authorised to. I started uat on my setup yesterday, and it's working so far. I do have to add more groups to the allowed to access for larger adoption, but I'm testing different scenarios at the moment and for security and what the benefit is and what hindrance the users could suffer.
... View more