Stub SAML Identity Provider (IdP)
The Stub SAML Identity Provider library allows users to easily spin up stub SAML IdP servers in test environments.
This is not a "real" IdP and should not be used in production environments. It is intended only for use in testing environments.
Installation and Usage
Add this to the Gemfile of your Rails app in your test environment:
Add to your
routes.rb file, for example:
get '/saml/auth' => 'saml_idp#new' post '/saml/auth' => 'saml_idp#create'
Create a controller that looks like this, customize to your own situation:
class SamlIdpController < StubSamlIdp::IdpController before_action :find_account # layout 'saml_idp' def idp_authenticate(email, password) user = @account.users.where(:email => params[:email]).first user && user.valid_password?(params[:password]) ? user : nil end def idp_make_saml_response(user) encode_SAMLResponse(user.email) end private def find_account @subdomain = saml_acs_url[/https?:\/\/(.+?)\.example.com/, 1] @account = Account.find_by_subdomain(@subdomain) render :status => :forbidden unless @account.saml_enabled? end end
The most minimal example controller would look like:
class SamlIdpController < StubSamlIdp::IdpController def idp_authenticate(email, password) true end def idp_make_saml_response(user) encode_SAMLResponse("firstname.lastname@example.org") end end
Keys and Secrets
To generate the SAML Response it uses a default X.509 certificate and secret key... which isn't so secret. You can find them in
SamlIdp::Default. The X.509 certificate is valid until year 2032. You can customize these values by setting the properties
secret_key using a
prepend_before_action callback within the current request context or setting them globally via the
The fingerprint to use, if you use the default X.509 certificate of this gem, is:
To act as a Service Provider which generates SAML Requests and can react to SAML Responses use the excellent ruby-saml gem.
This is an updated version of the stub SAML IDP originally published by Lawrence Pit. The updated gem would not have been possible without his contribution.
Copyright (c) 2022 Peter M. Goldstein See MIT-LICENSE for details. Copyright (c) 2012 Lawrence Pit. See MIT-LICENSE for details.