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
Copy file name to clipboardExpand all lines: README.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,14 @@
3
3
4
4
## Updating from 0.9.x to 1.0.X
5
5
6
-
Version `1.0` is a recommended update for all Ruby SAML users since include security fixes.
7
-
Adds security improvements like entity expansion limitation, more saml message validations and other important improvements like decrypt support. For more details, please review [the changelog](changelog.md). Also notice that in this version the get_idp_metadata method raise an exception when not able to fetch the idp metadata, so review your integration if you are using this functionality.
6
+
Version `1.0` is a recommended update for all Ruby SAML users as it includes security fixes.
7
+
8
+
Version `1.0` adds security improvements like entity expansion limitation, more SAML message validations, and other important improvements like decrypt support.
9
+
10
+
For more details, please review [the changelog](changelog.md).
11
+
12
+
### Important Changes
13
+
Please note the `get_idp_metadata` method raises an exception when it is not able to fetch the idp metadata, so review your integration if you are using this functionality.
8
14
9
15
## Updating from 0.8.x to 0.9.x
10
16
Version `0.9` adds many new features and improvements.
@@ -24,7 +30,7 @@ We created a demo project for Rails4 that uses the latest version of this librar
24
30
* 1.8.7
25
31
* 1.9.x
26
32
* 2.1.x
27
-
* 2.2.0
33
+
* 2.2.x
28
34
29
35
## Adding Features, Pull Requests
30
36
* Fork the repository
@@ -41,7 +47,7 @@ Using `Gemfile`
41
47
42
48
```ruby
43
49
# latest stable
44
-
gem 'ruby-saml', '~> 0.9'
50
+
gem 'ruby-saml', '~> 1.0.0'
45
51
46
52
# or track master for bleeding-edge
47
53
gem 'ruby-saml', :github => 'onelogin/ruby-saml'
@@ -123,7 +129,7 @@ end
123
129
124
130
In the above there are a few assumptions in place, one being that the response.nameid is an email address. This is all handled with how you specify the settings that are in play via the saml_settings method. That could be implemented along the lines of this:
125
131
126
-
If the assertion of the SAMLResponse is not encrypted, you can initialize the Response without the :settings parameter and set it later,
132
+
If the assertion of the SAMLResponse is not encrypted, you can initialize the Response without the :settings parameter and set it later,
0 commit comments