SAP AS Java Administration · Logon Procedures & Single Sign-On

Walk through how the standard ticket stack (EvaluateTicketLoginModule SUFFICIENT, BasicPasswordLoginModule REQUISITE, CreateTicketLoginModule OPTIONAL) authenticates a user.

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Logon Procedures & Single Sign-On

In the AS Java JAAS implementation, what is a login module and how does it relate to an authentication stack?

Of the AS Java logon procedures, which are SAP-proprietary rather than open standards?

Which authentication stack is delivered as the standard logon procedure for Web Dynpro and most AS Java applications, and why does that matter to an admin?

You need two Web Dynpro Java applications on the same AS Java to use different logon procedures. Can you configure them separately?

For login module flags, what is the difference between SUFFICIENT and REQUISITE in how control returns to the application?

Which AS Java login module issues logon tickets and which one verifies tickets issued by other servers?

Start learning today

Free to start — download the app or use it in your browser.