cancel
Showing results for 
Search instead for 
Did you mean: 

Correct Authorization Object / Configuration for Deregistration / Account Deletion of Candidates

patrickvogt
Explorer

Hi there,

I am currently searching for the right authorization configuration for the "self-deregistration" / "self-account deletion" of candidates. The candidate can deregister himself/herself in the candidate cockpit, but there is an authorization needed for the user (or a reference user) to lock his/her corresponding user. So after debugging that part of the application I came to the conclusion that the following authorization configuration is needed: S_USER_GRP (ACTVT=05 and CLASS=PBEX). Is this really the right authorization configuration in this case? Since the system is accessible publicly I just wanted to ask if anyone knows a "less strong" configuration for the authorization such that the candidates are still able to deregister themselves in the candidate cockpit.

Best Regards and thanks in advance

Accepted Solutions (0)

Answers (1)

Answers (1)

patrickvogt
Explorer

I somehow cannot edit my post.

Some additions:

1. The E-Recruiting system is not separated into a frontend and backend system in this case.

2. S_USER_GRP => Authorization for User Groups, ACTVT=05 (Locking of Users), CLASS=PBEX (User Group for External Users)