You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 12, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+31-7Lines changed: 31 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ We created a demo project for Rails4 that uses the latest version of this librar
18
18
* 1.8.7
19
19
* 1.9.x
20
20
* 2.1.x
21
-
* 2.2 (not yet officially supported)
21
+
* 2.2.0
22
22
23
23
## Adding Features, Pull Requests
24
24
* Fork the repository
@@ -41,7 +41,7 @@ gem 'ruby-saml', '~> 0.9.1'
41
41
gem 'ruby-saml', :github => 'onelogin/ruby-saml'
42
42
```
43
43
44
-
Using Bundler
44
+
Using RubyGems
45
45
46
46
```sh
47
47
gem install ruby-saml
@@ -58,6 +58,22 @@ or just the required components individually:
58
58
require'onelogin/ruby-saml/authrequest'
59
59
```
60
60
61
+
### Installation on Ruby 1.8.7
62
+
63
+
This gem has a dependency on Nokogiri, which dropped support for Ruby 1.8.x in Nokogiri 1.6. When installing this gem on Ruby 1.8.7, you will need to make sure a version of Nokogiri prior to 1.6 is installed or specified if it hasn't been already.
64
+
65
+
Using `Gemfile`
66
+
67
+
```ruby
68
+
gem 'nokogiri', '~> 1.5.10'
69
+
```
70
+
71
+
Using RubyGems
72
+
73
+
```sh
74
+
gem install nokogiri --version '~> 1.5.10'
75
+
````
76
+
61
77
## The Initialization Phase
62
78
63
79
This is the first request you will get from the identity provider. It will hit your application at a specific URL (that you've announced as being your SAML initialization point). The response to this initialization, is a redirect back to the identity provider, which can look something like this (ignore the saml_settings method call for now):
@@ -192,7 +209,7 @@ The following attributes are set:
192
209
* idp_slo_target_url
193
210
* id_cert_fingerpint
194
211
195
-
If are using saml:AttributeStatement to transfer metadata, like the user name, you can access all the attributes through response.attributes. It contains all the saml:AttributeStatement with its 'Name' as a indifferent key the one/more saml:AttributeValue as value. The value returned depends on the value of the
212
+
If you are using saml:AttributeStatement to transfer metadata, like the user name, you can access all the attributes through response.attributes. It contains all the saml:AttributeStatement with its 'Name' as a indifferent key the one/more saml:AttributeValue as value. The value returned depends on the value of the
196
213
`single_value_compatibility` (when activate, only one value returned, the first one)
197
214
198
215
```ruby
@@ -320,16 +337,23 @@ In order to be able to sign we need first to define the private key and the publ
320
337
The settings related to sign are stored in the `security` attribute of the settings:
321
338
322
339
```ruby
323
-
settings.security[:authn_requests_signed] =true# Enable or not signature on AuthNRequest
324
-
settings.security[:logout_requests_signed] =true# Enable or not signature on Logout Request
340
+
settings.security[:authn_requests_signed] = true# Enable or not signature on AuthNRequest
341
+
settings.security[:logout_requests_signed] = true# Enable or not signature on Logout Request
325
342
settings.security[:logout_responses_signed] = true# Enable or not signature on Logout Response
343
+
settings.security[:metadata_signed] = true# Enable or not signature on Metadata
0 commit comments