This message was deleted.
# platform-blueprintss
Slackbot
07/03/2023, 12:29 PMThis message was deleted.
a
Andrew Fong
07/03/2023, 1:19 PMFWIW I don’t think you want RBAC if you’re in enterprise. You actually want FGAC. This post seems written way more for a mid-market / single product / few team type approach.
Andrew Fong
07/03/2023, 1:21 PMAre you interested in the technical details or the process/policy details? The technical is pretty straightforward and the IDP most likely is just a consumer of data from other systems. You want a single source of truth and its most likely not the IDP for policy data. If you’re using Auth0 / Okta you can map things into the IDP and manage most of this externally.
a
Anshul Garg
07/05/2023, 5:41 AMCurrently, we are utilizing Backstage as our platform. Within Backstage, we have various microservices that are maintained by different teams. Moreover, our organization employs OKTA as a Single Sign-On (SSO) solution.
To integrate Backstage with OKTA, we have configured Backstage to connect with the SSO. Additionally, we have modified the Backstage permission framework to grant relevant access to microservices for individual team members. This access is determined based on the LDAP group associated with their OKTA profiles. We have extended the functionality of the Backstage permission framework to enable this setup. However, it appears that Port offers a more configuration-driven approach to handle similar requirements, which may be easier to implement.
t
Thian
07/10/2023, 2:40 AMthanks for the info guys
a
abhijith K
07/13/2023, 6:58 AM@Anshul Garg With Okta, its pretty expensive?
a
Anshul Garg
07/13/2023, 7:12 AM@abhijith K Yeah OKTA is pretty expensive but other built-in options are also available.
Refer over here https://backstage.io/docs/auth/
s
Shivkumar
08/02/2023, 9:20 AMIDC Is any document we got
y
Yair Siman Tov
08/09/2023, 10:16 AMHello there 👋,
I’m Yair, a developer at Port R&D. As previously discussed, we have Role-Based Access Control (RBAC) permissions for all port objects within our system.
Our list of supported Single Sign-On (SSO) options is continuously expanding. This includes platforms like Okta, Azure AD, Onlogin, and JumpCloud.
With these permissions in place, managing access rights within Port becomes a straightforward process.
Would love to help with anyone who is trying to integrate with port or you can also do it yourselves using our SSO Providers & RBAC documentations
45 Views