SPM integration with CUP 5.3

Question

All the issues regarding SPM integration with CUP is resolved, with the exception of one which is mentioned below:
Any user can go and raise a request for the FF ID from CUP Super User Access workflow, and are created in the backend, but they do not get the access to FF ID when trying to Login.
My query: is there any means to capture the user detail much in advance while the request is processed in the workflow and reject the request before it could be created and stored in backend.
Ideally The user not having minimum privilege of u201C/VIRSA/Z_VFAT_FIREFIGHTERu201D should not Login with the FF ID, which is met here, but this is checked only after the user get the access to FF ID and try to LOG into FF ID using his Login detail.
Please put some clarity on this.
Thanks,
Abhimanu Singh

Answer 1

Hi Sabita,
Thanks for the reply but this do not answer my question. Let me come in detail on this topic:
SAP Backend:
We have FF ID Owner, FF ID Controller, FF ID and Firefighters in the Backend.
FF ID owner has the minimun role required for becoimng the owner is /VIRSA/Z_VFAT_ID_OWNER.
FF ID Controller created with the minimum role /VIRSA/Z_VFAT_ID_OWNER for the monitoring purpose of all the reports.
FF ID is defined with the defined task in the role being assigned to it.
Firefighter is created with the minimum role /VIRSA/Z_VFAT_FIREFIGHTER to get the access to FF ID for the limited period as defined by the FF ID Owner.
For example:
FF ID Owner: User ID is FFO
FF ID Controller: User ID is FFC
FF ID: User ID is FID
Firefighter: User ID is FFS
Now the Question is from
SAP Frontend Java stack
I can see that the users(other than FFS) who are not defined as firefighter in the backend can still go and put a request for the FF ID access and gets provisioned.
When you go and check in the backend with the firefighter Owner ID/FF Administrator ID you can see the requested user listed there with the limited time period in the firefighter list.
Now comes the real picture: when this user(other than FFS) tries to login using his user ID he will not get the FF ID Login link on the page which is ideally correct. This is because any user not defined as firefighter in the backend with the minimum role /VIRSA/Z_VFAT_FIREFIGHTER should not get the access to FF ID.
My question comes here:
Is there any option in the frontend which could inform the user (other than FFS) much in advance and stop him requesting for the FF ID which has no meaning since it is finally not going to get the access in the backend to the FF ID.
Please get back to me if you require some more information.
Thanks,
Abhimanu Singh