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
+22-1Lines changed: 22 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,6 +178,7 @@ At *java-saml-tookit-jspsample/src/main/resources* folder is the *onelogin.saml.
178
178
#### Settings
179
179
First of all we need to configure the toolkit. The SP's info, the IdP's info, and in some cases, configuration for advanced security issues, such as signatures and encryption.
180
180
181
+
##### Properties File
181
182
All the settings are defined in one unique file; by default, the Auth class loads a *onelogin.saml.properties* file with the Auth() method, but if we named it in a different way, we can use Auth(filename);
182
183
183
184
Here are the list of properties to be defined on the settings file:
@@ -337,7 +338,27 @@ onelogin.saml2.organization.lang = en
337
338
onelogin.saml2.contacts.technical.given_name = Technical Guy
It is possible to build settings programatically. You can load your values from different sources such as files, databases, or generated values.
346
+
347
+
The `SettingsBuilder` class exposes the method `fromValues(Map<String, Object> samlData)` which let you build your settings dynamically. The `key` strings are the same from the *Properties file*
0 commit comments