AnsweredAssumed Answered

Joiner process when multiple business are involved

Question asked by Jesvin Joseph on Oct 24, 2018
Latest reply on Oct 25, 2018 by Boris Lekumovich

Like • Show 0 Likes0
Comment • 3

Hi,

We are planning to on-board a new business B (which uses different HR source and different AD/Exchange domains) into L&G. The existing business A in L&G, uses an attribute change rule (which triggers when new users are detected) to trigger WF's for provisioning default birthright access.

If we on-board the new business, the above rule will get triggered (for business A) even if a new user on-boards in the new business B (and vice versa if the same config is applied for the new business). One way to stop this doing any provisioning is to filter it out in the WF, but still it would trigger an unwanted change request.

What would be the best way to sort this out.?

No one else has this question

Outcomes

Boris Lekumovich

Oct 24, 2018 3:14 AM

I assume you are using "When new users are detected" option.

You are limited with that design.

You might get away with changing the WF, but it might get out of hand when there will be new business C,D,E...

A more flexible approach might be to use roles to grant default birthright access

Actions

Jesvin Joseph @ Boris Lekumovich on Oct 25, 2018 1:04 AM

Thanks Boris. Yes, we are using the "when new users are detected option" and is looking forward to adding more businesses into the system.

Can you please help me on how to trigger change requests by making use of roles, when new users are detected. I am pretty new to the roles concept.

Actions

Boris Lekumovich

@ Jesvin Joseph on Oct 25, 2018 3:30 AM

I highly recommend to start with some relevant training:

RSA Identity Governance & Lifecycle: Role Management Fundamentals

RSA Business Role Manager

I also recommend to have a roles workshop with some from RSA to get a better understating and best practices.

With regards to your question, have a look at the screenshot below.

You can configure a Membership Rule

When a user matches a specific rule (which was defined in the role) will be identified, it will be added to the role (and will get the relevant authorizations).

The is controlled by the Create change requests configuration

1 person found this helpful

Actions

3 Replies

Boris Lekumovich Oct 24, 2018 3:14 AM
Mark Correct
Correct Answer
I assume you are using "When new users are detected" option.

You are limited with that design.
You might get away with changing the WF, but it might get out of hand when there will be new business C,D,E...

A more flexible approach might be to use roles to grant default birthright access
Like • Show 0 Likes0
Actions
- Jesvin Joseph @ Boris Lekumovich on Oct 25, 2018 1:04 AM
  Mark Correct
  Correct Answer
  Thanks Boris. Yes, we are using the "when new users are detected option" and is looking forward to adding more businesses into the system.
  
  Can you please help me on how to trigger change requests by making use of roles, when new users are detected. I am pretty new to the roles concept.
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Jesvin Joseph on Oct 25, 2018 3:30 AM
    Mark Correct
    Correct Answer
    I highly recommend to start with some relevant training:
    RSA Identity Governance & Lifecycle: Role Management Fundamentals
    RSA Business Role Manager
    
    I also recommend to have a roles workshop with some from RSA to get a better understating and best practices.
    
    With regards to your question, have a look at the screenshot below.
    You can configure a Membership Rule
    When a user matches a specific rule (which was defined in the role) will be identified, it will be added to the role (and will get the relevant authorizations).
    The is controlled by the Create change requests configuration
    
    1 person found this helpful
    Like • Show 0 Likes0
    Actions

Joiner process when multiple business are involved

Outcomes

Related Content

Recommended Content