Skip to content
AEA.Ali Emre Altuntaş
← All integration projects
SAPLDAP

Sign in to a portal with a company account.

An employee enters their username and password in the portal. I built the SAP connection that checks whether the company account is active and the password is correct. If both checks pass, the portal opens a session. A wrong password or a disabled account prevents sign-in.

A directory of accounts connected to SAP

What happens after you enter your password?

The first SAP screen shows the two details the portal sends. The second shows the recorded outcomes for a correct password, an incorrect password and a disabled account.

Who does what during sign-in?

The portal checks company credentials through SAP and receives the result from the directory.

The portal asks and the directory checks

The person signs in to the portal with a company account. The SAP connection checks the account state and password against the company directory.

The portal uses the result

A valid sign-in, a wrong password and a disabled account produce different outcomes. The portal uses the returned result to start a session or turn the request down.

What I built

Recognise the company account
I built the connection that checks a portal user’s credentials against the company directory. When a mapping exists, the result also identifies the corresponding SAP user.
Limit repeated sign-in attempts
After repeated incorrect passwords, my check delays the next attempt and tells the portal how long to wait before retrying.When someone retries a wrong password
Help support trace sign-in problems
Administrators can review successful checks, disabled accounts and incorrect passwords without logging passwords. They can preview the effect of clearing old records.Review the outcomes

From the test screens

01 / 03

When someone retries a wrong password

The test first reports a wrong password. After repeated attempts, it reports that the caller must wait.

Test output showing wrong password followed by too many attempts.View full size ↗
  • A“WRONG_PASSWORD” means the supplied password failed the check.
  • B“TOO_MANY_ATTEMPTS” tells the portal to wait before retrying.
02 / 03

Preview maintenance before changing records

An administrative test run previews the effect on old records and expired counters. The first line confirms that nothing was deleted during this run.

Test-run result stating that nothing was deleted, followed by a counter summary.View full size ↗
  • A“Test run: nothing deleted.” confirms that SAP only previewed the cleanup.
03 / 03

Support can see when the wait ends

The test record shows the number of failed attempts and the time of the last one. The blocked row also shows when another attempt is allowed.

SAP administration view with failure counts and the time a block expires.View full size ↗
  • AThe last column shows when another attempt is allowed. In this row the wait ends at 10:53:28.