nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Single Sign-On (SSO) stopped working after upgrading WAB from 2.17 to 2.20 due to bug in API 4.19 and 4.20

MichaelLev

Our company 3D Scenes Web Apps are developed by WAB (Develper Edition). Its current version is 2.20

Our customers do not log in directly to our server, but we use "Single Sign On" and they login by active directory authentication, using Azure, and the login dialog box presents a choice - whether to login as a regular user, via azure, or directly into the portal server. Regular users login via azure.

After upgrading from WAb 2.17 to WAB 2.20, the "Single Sign On" does not function at all - the dialog box contains only the option to login directly into the portal server, which is NOT how a regular user should enter

Encuentra más publicaciones etiquetadas con

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.