Skip to content

Update AMS SNOW component #29

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
f-blass merged 1 commit into from
Apr 8, 2026
Merged

Update AMS SNOW component #29

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/Support.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ As registered SAP customers, report your issue by creating a ticket on the [SAP
| Name | Service Now Component | Description |
| --------------------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------|
| Identity Authentication Service (**IAS**) | BC-IAM-IDS | SCI tenant, User Management, Token Flows, Technical Communication etc. |
| Authorization Management Service (**AMS**) | BC-IAM-CAS | AMS Server, Authorization Management UI, DCL compiler, buildpack, bundle gateway |
| Authorization Management Service (**AMS**) | BC-IAM-AMS | AMS Server, Authorization Management UI, DCL compiler, buildpack, bundle gateway |
| Security Client Libraries | BC-CP-CF-SEC-LIB | Java, Node.js and Go client libraries for SAP Cloud Identity Services, Authorization Management, XSUAA |
| BTP `identity` Service Broker | BC-IAM-IB | Service creation of SAP Cloud Identity Services instances on BTP |

Expand All @@ -49,4 +49,4 @@ Make sure that you include the following information in the support ticket to gi
- For unexpected authentication results (401 or Error): the relevant **debug log output** of the token validation in the libraries
- For unexpected authorization results (403 or too many privileges): the relevant **debug log output** of the privilege check in the libraries for Authorization Management that you don't understand
- Potential steps you have already tried to fix the problem
- Reason why you believe it's a bug
- Reason why you believe it's a bug
Loading