Start a SAML SP Test
Connect to a remote IdP and use this environment as a SAML service provider. After login, you can inspect the IdP EntityID, NameID, SessionIndex, and returned attributes.
Choose SAML SP testing or SAML IdP testing based on the system you want to connect to. Each mode lets you register metadata, run an SSO login flow, and inspect NameID and exchanged attributes during the test.
Connect to a remote IdP and use this environment as a SAML service provider. After login, you can inspect the IdP EntityID, NameID, SessionIndex, and returned attributes.
Connect to a remote SP and use this environment as a SAML identity provider. Fixed test users help you verify which attributes and multi-value claims the SP receives.
These are the entry URLs for the guide page, SP testing, and IdP testing. When you need metadata or SAML endpoints, open the page for the mode you want to test.
SP testing supports pasted metadata XML, metadata URLs, XML file uploads, and manual minimum-field registration for remote IdPs.
You can switch Binding, RequestedAuthnContext, ForceAuthn, isPassive, NameIDPolicy, IDPList, Audience, and signed-request behavior before sending the request.
SP testing shows NameID, SessionIndex, and returned attributes, plus signature verification and encrypted-assertion decryption results for the SAML Response.
IdP testing lets you register remote SP metadata, publish this environment's IdP metadata, and run IdP-initiated logins with fixed test users.
Use this page when you first need to decide whether your integration test should treat this environment as the SP or the IdP. It is the best starting point for metadata exchange checks, SSO round trips, and attribute inspection.
The remote system is an IdP. Your main checks are AuthnRequest behavior, ACS, NameID, SAML Response handling, signature verification, and returned attributes.
The remote system is an SP. Your main checks are IdP metadata, SSO / SLO endpoints, fixed-user attribute release, and what the SP receives after login.
If you already know the role you need, start with the dedicated public guide for a shorter setup path.
The main-site docs section also includes focused guides for SP testing, IdP testing, and metadata review.
Review EntityID, ACS, AuthnRequest, and attribute checks for SP-side testing.
Review SSO, SLO, fixed users, and the SP-side checks that matter most.
Check EntityID, ACS / SSO / SLO endpoints, certificates, and NameID assumptions before testing.
It validates metadata exchange, SSO login flows, NameID and attribute handling, SLO endpoint visibility, and common AuthnRequest options.
Use SP testing when the remote side is an IdP, and use IdP testing when the remote side is an SP. That decision changes which metadata you exchange and what you should verify.
The public guide pages are indexable, shareable documentation pages. The actual metadata registration and login actions happen on the noindex test consoles at sp.samltest.kmmr.jp and idp.samltest.kmmr.jp.
In SP testing, you can inspect returned attributes, NameID, SessionIndex, signature verification results, and decrypted content when needed.
Yes. You can start from pasted XML, file upload, or manual minimum-field entry when a metadata URL is not available.