Home > General Administration > Managing Dashboard Access > SAML Login History Events

SAML Login History Events

SAML login history can be used to track successful SAML logins and troubleshoot SAML login failures. This log is located on the Organization > Administrators page under the SAML administrator roles section. It contains error messages, and in some instances, the XML POST to the consumer URL. This article defines events and their cause. This article does not cover IdP authentication issues, as this is outside the scope of the Cisco Meraki SP, nor does it cover events related to an incorrectly configured consumer URL on the IdP.

  

 

For information on how to configure, refer to the article on SAML Integration with Dashboard

    

When a user is successfully authenticated by the IdP but fails to log-in to Dashboard, the following message will appear in the user's web browser. In most instances an error message related to the failure will appear in SAML login history.

56f8a646-cadd-4f21-ac2e-5ce304e426bd

Each event in the log contains the following information:

 

  • Status: Green icon means there was a successful SAML login. Red icon means the SAML login failed.
  • Time: The time in UTC at which the SAML login occurred.
  • Source IP: The IP address of the client that sent the POST to the Dashboard consumer URL, as seen by Dashboard.
  • Username: The value specified in the username assertion, if present.
  • Role: The value specified in the role assertion, if present.
  • Errors: The reason for the login failure, or 'none' if successful.

 

Click on any event to see Login details. From the Login details the Status of the login can be checked. The status will either be Success or Failed. Additionally, you can click Full XML to see the users XML POST to the consumer URL.

Success Events

When a successful SAML login occurs, an event will appear in the SAML login history. The event will show the username assertion and role assertion associated with the login. The Error column will indicate 'none' because no errors occurred.

 

48d4c659-3070-4a8e-b353-ea4e8bed93f7

Failure Events

This section will cover a variety of errors that may appear in the log, as well as their most likely causes. Specific details on how to fix these errors will vary dependent on the IdP being used.

Assertion validation error: Certificate element missing in response (ds:X509Certificate)

90bb25c6-d62b-40ed-a2f4-b0cb7fe61227

The IdP is not using a token-signing certificate or the certificate is missing in the assertion. Verify the IdP is using a valid token-signing certificate and then check the Full XML to determine if the X.509 certificate is included in the assertion.

Assertion validation error: Fingerprint mismatch

5e869fff-0e5e-4151-b52e-3c2a6955e064

The configured X.509 cert SHA1 fingerprint value in Dashboard does not match the SHA1 fingerprint of the token-signing certificate of the IdP. Verify the SHA1 fingerprint in the token-signing certificate used by the IdP matches the configured SHA1 fingerprint configured in Dashboard.

Assertion contains no username and no role

111eb68a-ad8f-4ac2-a45d-7ac91ffc17ec

The user POST to the consumer URL does not contain a valid username and role assertion. Verify the POST contains a valid username and role assertion name and value. To look at the XML assertions for the login event, click on the event and then Full XML. In the example XML output both assertions are present and valid. There is a username of "supportlab11@ikarem.com" and a role name of "saml_admin" which is also a configured role Dashboard. 

 

c71c7fa4-25b5-4b55-9726-e81999124c9d

Assertion contains no role

c452c504-cbaa-4c09-b9d9-d773bc90cc83

The user POST to the consumer URL does not contain a valid role assertion. The event will show the sent username assertion, but the role assertion is missing completely or the role assertion name is invalid. To view the assertion, click on the login event, then Full XML . Verify the POST contains a valid role assertion name and value. In the example below, the role assertion value is "saml_admin".

6ba915fe-5c7b-42ea-87ad-f8ffadb34d90

Assertion specifies role that does not exist

6095da97-a11e-48d5-8a55-5fd1268fad94

The user POST to the consumer URL does not contain a role assertion value which matches a configured role value in Dashboard. Check the Role column under the SAML administrator roles section in Dashboard and find the correct role. To view the assertion, click on the login event, then Full XML . Verify the POST contains a role assertion value which matches the configured role in Dashboard.

 

In this screenshot, the role assertion being sent is supportlab11.

f8053ec3-0587-4428-88e7-1e1697867194

The only roll that exists in Dashboard is named "saml_admin", as shown below.

c0e19c0d-1961-4c42-b611-9630cca6e832

Therefore the role assertion should contain a value of saml_admin

7f1151e7-79bd-4a14-8a19-c3a3c1b62aad

No SAMLReponse provided

5fb971aa-0806-435f-b70c-a7a9eadfd91c

Something sent an HTTP GET to the consumer URL but never attempted a SAML login. Pasting the consumer URL into any web browser, without first going through the IdP, will generate this event.

You must to post a comment.
Last modified
18:11, 4 Mar 2016

Tags

Classifications

This page has no classifications.

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community