GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - Blueleaf/saml_service_provider

BranchesTags
Open more actions menu

Latest commit

 

History

54 Commits
54 Commits

Folders and files

NameName
Last commit message
Last commit date
.github
.github
 
 
app
app
 
 
bin
bin
 
 
config
config
 
 
db
db
 
 
lib
lib
 
 
log
log
 
 
public
public
 
 
test
test
 
 
tmp
tmp
 
 
vendor/assets
vendor/assets
 
 
.gitignore
.gitignore
 
 
Gemfile
Gemfile
 
 
Gemfile.lock
Gemfile.lock
 
 
README.md
README.md
 
 
Rakefile
Rakefile
 
 
config.ru
config.ru
 
 

Repository files navigation

README

This is a sample application implementing Blueleaf's Single Sign-On Servie Provider specification, using Blueleaf as the Identity Provider (IdP).

The key parameters are as follows:

settings = OneLogin::RubySaml::Settings.new

settings.idp_entity_id                  = "https://secure.blueleaf.com/sso/sign_in"
settings.idp_sso_target_url             = "https://secure.blueleaf.com/sso/sign_in"
settings.idp_cert_fingerprint           = "0de3c93f93e02ad3764f9dbd21a80edac6b1521b6f78bcbfbe9558bce1226c88"
settings.idp_cert_fingerprint_algorithm = "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"
settings.name_identifier_format         = "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"

Contact [email protected] with your SSO initialization endpoint, and your logo.

In plain English:

  • Our SSO Entity ID and target url are https://secure.blueleaf.com/sso/sign_in
  • The certificate digest is pre-shared statically.
  • Use SHA-256 to verify our certificate against the digest
  • The NameId is stable, and is formatted as an integer.
  • The authentication flow is:
    • User logs in to Blueleaf
    • User click on partner's logo
    • Binding Option
      • User is redirected to partner authentication page
      • User authenticates with partner
      • Partner binds Blueleaf's NameId to the authenticated user
    • Auto-provisioning Option
      • Partner creates local user from supplementary data sent (TBD)
      • Partner binds new user to Blueleaf NameId
    • Partner displays or redirects user to the expected landing page
  • on future connections
    • partner looks up user binding to Blueleaf NameId
    • partner bypasses prompting for credentials if binding is found
    • partner redirects user to expected landing page

About

No description, website, or topics provided.

Resources

Readme
Activity
Custom properties

Stars

0 stars

Watchers

11 watching

Forks

1 fork
Report repository

Releases

Packages

Used by

Contributors

Languages

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.