How to Check OIDC Protocol Assertions and Use Them for Troubleshooting
Share

In this blog, we’ll explore how to inspect OIDC (OpenID Connect) protocol assertions and leverage them for effective troubleshooting.

Prerequisite

Before diving into the troubleshooting steps, note that I have already configured Single Sign-On (SSO) between SAP Identity Authentication Service (IAS) and an S/4HANA system using the OIDC protocol.

Step 1: Activate Security Trace

  • Launch transaction SECTRACE.
  • Enable the trace for the SICF path:
    /sap/public/bc/sec/oidc/redirect.

muthu_kumar_1-1754280167021.png

 

Step 2: Trigger the SSO Flow

  • Access the S/4HANA Fiori Launchpad using SSO to initiate the authentication flow.

muthu_kumar_2-1753126404370.png

 

Step 3: Retrieve the Security Trace

  • Go back to transaction SECTRACE, stop the trace, and click Show.
  • In the user field, enter <ALL> and confirm

muthu_kumar_3-1753126523092.png

  • Click the down arrow to expand the trace details.

muthu_kumar_5-1753126724345.png

  • Copy the complete OIDC response for further analysis.

muthu_kumar_6-1753126817567.png

Step 4: Analyze the OIDC Token

  • Run transaction SOIDC_ANALYZER.
  • Paste the copied OIDC token into the input field.

muthu_kumar_8-1753127089438.png

  • Click Extract Token from Trace Snippet, then select Analyze and Pretty-print Token Content.

muthu_kumar_9-1753127322182.png

  • This will display the OIDC assertions in a readable format.

muthu_kumar_2-1754280240027.png

Step 5: Modify and Test OIDC Configuration

Use the highlighted section in the analyzer tool to adjust existing OIDC settings and re-check the responses as needed during troubleshooting.

muthu_kumar_0-1753128046381.png

This approach helps in identifying issues in the OIDC authentication flow and validating token content for debugging and support purposes.

References:

3111813 – OpenID Connect (OIDC): Troubleshooting Note – SAP for Me

 

 In this blog, we’ll explore how to inspect OIDC (OpenID Connect) protocol assertions and leverage them for effective troubleshooting.PrerequisiteBefore diving into the troubleshooting steps, note that I have already configured Single Sign-On (SSO) between SAP Identity Authentication Service (IAS) and an S/4HANA system using the OIDC protocol.Step 1: Activate Security TraceLaunch transaction SECTRACE.Enable the trace for the SICF path:/sap/public/bc/sec/oidc/redirect. Step 2: Trigger the SSO FlowAccess the S/4HANA Fiori Launchpad using SSO to initiate the authentication flow. Step 3: Retrieve the Security TraceGo back to transaction SECTRACE, stop the trace, and click Show.In the user field, enter <ALL> and confirmClick the down arrow to expand the trace details.Copy the complete OIDC response for further analysis.Step 4: Analyze the OIDC TokenRun transaction SOIDC_ANALYZER.Paste the copied OIDC token into the input field.Click Extract Token from Trace Snippet, then select Analyze and Pretty-print Token Content.This will display the OIDC assertions in a readable format.Step 5: Modify and Test OIDC ConfigurationUse the highlighted section in the analyzer tool to adjust existing OIDC settings and re-check the responses as needed during troubleshooting.This approach helps in identifying issues in the OIDC authentication flow and validating token content for debugging and support purposes.References:3111813 – OpenID Connect (OIDC): Troubleshooting Note – SAP for Me Read More Technology Blog Posts by SAP articles 

#SAPCHANNEL

By ali