SSO with any Identity & Access Management (IAM) Solution via OpenID Connect (OIDC)
As a Security Administrator we want PRTG to integrate with our SSO system, but we do not use Entra ID or Okta. We need this so that we have control over users who joining or leaving the company to avoid having to manually manage users and permissions.
Use your IAM solution of choice with a generic OpenID Connect (OIDC) integration option.
Currently, we support Entra ID (formerly Azure AD) and Okta.
Hi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
-
Nicholas Hoyle
commented
As an IT Infrastructure Manager, I want to configure the group claim name in PRTG's OIDC token settings so that I can integrate PRTG with our organization's existing identity provider without requiring changes to our standardized OIDC claim naming conventions.
Currently, PRTG SSO Okta integration requires the claim name "groups" which is not flexible and cannot be used if you don't control the Okta setup or it is incompatible with standards in use. Other OIDC integrations (like Jira) allow you to set the name of the groups claim, so it can be compatible with your organizations OIDC setup. We would prefer to be able to name the groups claim to something else within the config of PRTG.