Hello Team,
Running into this access req. error but the issue is that this error can only be seen by the requester (request center).
I’ve tried search queries (type:access_request AND name:"Request Access Started" AND created:[*** TO now] also tried search with just the identity name/id) as well as checking the request activity under search/reports but all those only show basic access req info ( accessItemId, accountActivityId, sourceName, etc) - nothing about the workflow/error.
Also tried API req {baseUrl}}/access-request-status?requested-for=******" but the returned JSON/resp only shows basic info on the access req.
What’s the best way to see the full picture of an access req including ones submitted by someone else including errors, etc like the one in the screenshot?
We are experiencing the same unexpected error with the product tenant of our current customer. This issue affects all Access Profiles added since July 2024. The error occurs during the access request reviewing process after the Access Profiles have been deployed.
Request completed
An unexpected error occurred: AccessProfile with ID or name Access Profile with name: AP : something - something (Z_SD_something) [AccessProfile-1720585207346] & AP : something - something (Z_SD_something) not found in gov-role was not found.
We have created a support ticket for this issue and demonstrated the error to the engineering team.
For your case , i believe the issue is with the context URL. Are you using characters like + in the url ?
If so, can you please try to change it to the url encoded version so + will become %2B.
This seems very strange. Is there a possibility that the access profiles which are being tried for provisioning are no longer existing in the ISC.
I am thinking for the case, lets say when the role was requested the access profile was there in the system but for some reason the role assignment went into error state but then the access profile was deleted for some reason but ISC is keep on trying to reprovision the role.
But i am sure support team will be able to provide the valid reason. Please keep us also updated about the issue.
I have additionally discovered the following regarding the issue.
The unexpected error occurs not only with newly created Access Profiles and Roles but also with all exist Access Profiles, Roles objects. The commonality among the problematic cases is that the approval stages include governance groups, and it seems that this mapping cannot be read correctly when an approval request is created.
The support ticket request has been escalated, and many customers are experiencing inconvenience.
Hi @timahm,
The engineering team has successfully reproduced the issue and informed us that they are currently investigating it with other teams to find a solution.
Regards,
The engineering team deployed a fix in the sandbox environment, and the tests were successful. We hope to deploy it to the production environment after thorough validation. Additionally, we have requested the identification of the root cause of the current issue.
It seems that the root cause is that SP is restricting end users from adding leading or trailing spaces in access profiles and roles names. They are working to fix the spaces. However, this applies only for new access profiles and roles. However, we’ll have to manually update the existing ones. I tested for an access profile and the request works after removing the space.
