not that i have ever heard of, but there might be other guys here knowing more about it.
We currently maintain around 40 roles without any problems.
What's the number you have in mind when asking that question ?
As of now we have around 30+ roles, which may be increasing as per customer. Roles increases as per customer demand, as different teams handle different clients with specific roles.
we are kind of in a same boat.
We currently maintain roles for the infrastructure teams that manage the servers.
When we want to move forward to a more self-service type concept (hopefully with levaraging the BSA Portal) we also have the need to have roles per Application Team /Customers and that would potentially raise the number of roles to 300-400.
Besides the performance and the limits in the system, my main question is, what's the best approach to properly manage such a complex RBAC beast.
So what i'm trying to say is : "Glad you asked" :-)
There’s no limitation of the number of rbac roles that can be created.
In the documentation (Bladelogic 8.5) there is a limitation about the number of RBAC roles assign to one user from the Bladelogic platform when LDAP/AD is used : 200 roles for one user.
I was suggested there is no maximum to the number of roles. Over-complexity as it leads to a maintenance overhead and more complex queries to the database, which would create performance overhead.
So let's be clear what we are talking about here:
"Is there a limitation for number of roles to be created in RBAC ?"
There is no limit to how many roles can exist in the system.
is that the real question? or is the question:
"How many roles can a user be a member of?"
if that's the question then the documentation indicates that if a user is assigned to more that 200 roles you may experience some performance issues logging in. now, is that still the case in 8.5? i'll look into that.