The API now returns a link to the request access page of eIAM, configured only on the back end.
The UI does not care about it but I added an optional rendering of said link on the error toast. I decided against redirecting right away to make it obvious to the user what is happening.
The API now returns a link to the request access page of eIAM, configured only on the back end.
The UI does not care about it but I added an optional rendering of said link on the error toast. I decided against redirecting right away to make it obvious to the user what is happening.