saml-sp | SAML 2.0 service provider | Authentication library

by openlogic Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | saml-sp Summary

saml-sp is a Ruby library typically used in Security, Authentication applications. saml-sp has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Support for being a SAML 2.0 service provider in an HTTP artifact binding SSO conversation.

Support

Quality

Security

License

Reuse

Support

saml-sp has a low active ecosystem.

It has 6 star(s) with 2 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

saml-sp has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of saml-sp is current.

Quality

saml-sp has 0 bugs and 0 code smells.

Security

saml-sp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

saml-sp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

saml-sp is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

saml-sp releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 1090 lines of code, 59 functions and 15 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed saml-sp and discovered the below as its top functions. This is intended to give you an instant insight into saml-sp implemented functionality, and help decide if they suit your requirements.

Resolve an artifact .
Validate the response
Generates XML for an XML request
Generate an XML request
Evaluate the config block .
Returns the basic authentication for the authenticate .
Wraps HTTParty method .
Returns an issuer with the issuer .
Defines an artifact .
Set logger to the logger

Get all kandi verified functions for this library.

saml-sp Key Features

No Key Features are available at this moment for saml-sp.

saml-sp Examples and Code Snippets

No Code Snippets are available at this moment for saml-sp.

Community Discussions

Trending Discussions on saml-sp

Q: Azure AD B2C: SAML IDP initiated to OpenIdConnect, is it possible?

Getting a HTTP 404 CAS Server SingleLogoutService

QUESTION

Q: Azure AD B2C: SAML IDP initiated to OpenIdConnect, is it possible?

Asked 2021-Apr-12 at 16:55

Trying to setup a custom policy in my Azure AD B2C tenant, I need to communicate to an external IDP using SAML IDP initiated, so client can navigate to their dashboard and click to "my app" that goes against my B2C tenant, and authenticates the user and gets send to my application using OpenIdConnect, it is required to me to get it integrated using SAML between my client's dahsboard and my B2C tenant

I used this article as based to create my custom policy using SAML. As SP initiated (through my app in azure ad b2c) works, but now I need to get it working using IDP initiated. Also found this idp-initiated sample, but here I got 2 problems:

This is setting up "my app" as SAML application (protocol in my RelyingParty, not what I want)
If I change that one to use "OpenIdConnect" which is desired in my RelyingParty I get the following error in my logs:

Policy '< myPolicyName >' in tenant '< myTenant >' does not have a supported relying party protocol"

So wondering in this point, is this something that's supported? I also got this unsupported-saml-modalities from the documentation and the last bullet point says:

Identity provider-initiated sign-on, where the identity provider is Azure AD B2C.

So, not really sure if what I'm trying to accomplish is something valid, any help?

...

ANSWER

Answered 2021-Apr-12 at 16:55

It’s not possible, an Idp initiated flow cannot respond to an OIDC relying party, only a SAML relying party.

Secondly, as the doc states, the IdP must be B2C, and will not work for an external IdP federated to B2C.

Source https://stackoverflow.com/questions/67061703

QUESTION

Getting a HTTP 404 CAS Server SingleLogoutService

Asked 2020-Apr-22 at 20:50

I am testing the SLO aka Single Logout Service for HTTP Redirect SAML 2.0 binding. I am able to SSO successfully but I need a HTTP Redirect endpoint on CAS to point to from my SAML-SP for SLO. The endpoint I am getting a 404 is http://cas-server:8080/idp/profile/SAML2/Redirect/SLO.

For SSO, the endpoint http://cas-server:8080/idp/profile/SAML2/Redirect/SSO is working fine.

My CAS version is 5.0.6.

Here is a snippet from my Idp metadata xml with the endpoints for SLO and SSO :

...

ANSWER

Answered 2020-Apr-22 at 20:50

Based on the 5.0.x documentation, the following endpoints are supported:

Source https://stackoverflow.com/questions/61365570

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install saml-sp

You can download it from GitHub.
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: