SAP Knowledge Base Article - Preview

3268335 - Single Sign On (SSO) is not working on the first call of web-based transaction through SAP GUI when Edge browser control is enabled

Symptom

  • SSO is not working when opening a new window;
  • When executing a transaction for the first time in the same SAP GUI session (e.g? SOAMANAGER),  the logon screen appears;
  • If an user closes the Login windows (failed SSO window) and opens a new one and execute a web-based transaction (second call), the SSO works;
  • The MYSAPSSO2 cookie (from Logon ticket method) is only present in the second calling of Webview2;
  • Sometimes an initial window appears,  a "500 - internal server error" message flashes and it disappears in few seconds.
  •  login/ticket_only_by_https parameter is set as 0;

  • Following error message appears in the dev_icf trace (visible in the transaction ST11)  after first call:

    <Error info: "http://-------/sap/public/myssocntl">

    <Error message>: "No ticket was received by header"


Read more...

Environment

SAP GUI for Windows 770 (regardless patch level)

Microsoft Edge Webview2 version 105.0.1343.33 or lower

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP S/4HANA all versions

Keywords

SSO, Single Sign On, First call, Fail, Microsoft Edge WebView2 Runtime, browser control, HTML control, SAP GUI, MYSAPSSO2. , KBA , BC-FES-CTL , SAP GUI for Windows Controls , BC-MID-ICF , Internet Communication Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.