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
Version `0.8.0` changes the namespace of the gem from `Onelogin::Saml` to `Onelogin::RubySaml`. Please update your implementations of the gem accordingly.
4
+
Version `0.8.x` changes the namespace of the gem from `OneLogin::Saml` to `OneLogin::RubySaml`. Please update your implementations of the gem accordingly.
5
5
6
6
## Overview
7
7
@@ -15,7 +15,7 @@ This is the first request you will get from the identity provider. It will hit y
15
15
16
16
```ruby
17
17
definit
18
-
request =Onelogin::RubySaml::Authrequest.new
18
+
request =OneLogin::RubySaml::Authrequest.new
19
19
redirect_to(request.create(saml_settings))
20
20
end
21
21
```
@@ -24,7 +24,7 @@ Once you've redirected back to the identity provider, it will ensure that the us
To form a trusted pair relationship with the IdP, the SP (you) need to provide metadata XML
108
108
to the IdP for various good reasons. (Caching, certificate lookups, relaying party permissions, etc)
109
109
110
-
The class Onelogin::RubySaml::Metadata takes care of this by reading the Settings and returning XML. All
110
+
The class OneLogin::RubySaml::Metadata takes care of this by reading the Settings and returning XML. All
111
111
you have to do is add a controller to return the data, then give this URL to the IdP administrator.
112
112
The metdata will be polled by the IdP every few minutes, so updating your settings should propagate
113
113
to the IdP settings.
@@ -117,7 +117,7 @@ class SamlController < ApplicationController
117
117
# ... the rest of your controller definitions ...
118
118
defmetadata
119
119
settings =Account.get_saml_settings
120
-
meta =Onelogin::RubySaml::Metadata.new
120
+
meta =OneLogin::RubySaml::Metadata.new
121
121
render :xml => meta.generate(settings)
122
122
end
123
123
end
@@ -132,7 +132,7 @@ First, ensure that both systems synchronize their clocks, using for example the
132
132
Even then you may experience intermittent issues though, because the clock of the Identity Provider may drift slightly ahead of your system clocks. To allow for a small amount of clock drift you can initialize the response passing in an option named `:allowed_clock_drift`. Its value must be given in a number (and/or fraction) of seconds. The value given is added to the current time at which the response is validated before it's tested against the `NotBefore` assertion. For example:
0 commit comments