Rob is correct.
In layman’s terms what it means is that your application has to accept an alternate form of login (instead of just user/pass). SAML is a very complicated form of single sign on (SSO) and there are others more widely accepted, but not fully supported by all vendors.
In SAML2 (the current supported standard by compliant vendors), an authentication request is typically initiated when a user clicks a link in another application. That application will indicate the user’s intent to log into your application. Your application will send an authentication request to the calling application to verify they are actually logged into that system and if it sends you a correct response (along with an identifier for that user), then you look that user up in your system by that ID and grant them access, trusting the partner system has already vetted them.
To implement this, your application needs to be able to generate a metadata file, auth certificate, and able to parse the same from the other party. You will need to work with the other party and share metadata files that contain signing certificates, register theirs in your system and vice versa. From there you can trust and decrypt the messages sent back/forth in the Login, Logout, etc. workflow you initiate between systems.
Many vendors also support what we call a one-way-link which is much simpler so you might inquire as to that vendors’ ability to support an alternate form of single sign on (OAuth, OpenID Connect, one-way link, etc.). The one-way link is simply sharing some secret key or phrase that is used to encode some parameters in a URL (usually a user ID). When the link is clicked the caller passes needed information for you to verify the user and the calling system, then you permit access.
Enjoy and hope Rob’s links and my explanation help you out…
- Mike