Login to administration
Please login to the metadata administration using a local account (by default admin/admin).
15 |21 |
37 |Please login to the metadata administration using a local account (by default admin/admin).
15 |21 |
37 |Please select Identity Provider to authenticate with.
19 |27 |
" method="GET"> 28 |Generates new metadata for service provider. Output can be used to configure your 17 | securityContext.xml descriptor.
18 |24 | |
25 | |
31 | ||||||||||||||||||
34 | | 35 | When set to true the generated metadata will be stored in the local metadata manager. The value 36 | will be available 37 | only until restart of the application server. 38 | 39 | | 40 |||||||||||||||||||
43 | |
44 | |
47 | ||||||||||||||||||
50 | | 51 | Entity ID is a unique identifier for an identity or service provider. Value is included in the 52 | generated metadata. 53 | 54 | | 55 |||||||||||||||||||
58 | |
59 | |
62 | ||||||||||||||||||
65 | | 66 | Base to generate URLs for this server. For example: https://myServer:443/saml-app. The public 67 | address your server will be accessed from should be used here. 68 | 69 | | 70 |||||||||||||||||||
73 | |
74 | |
77 | ||||||||||||||||||
80 | | 81 | Alias is an internal mechanism allowing collocating multiple service providers on one server. 82 | When set, alias must be unique. 83 | 84 | | 85 |||||||||||||||||||
88 | |
89 | |
92 | ||||||||||||||||||
95 | | 96 | Key used for digital signatures of SAML messages. Public key will be included in the metadata. 97 | | 98 |||||||||||||||||||
101 | |
102 | |
105 | ||||||||||||||||||
108 | | 109 | Key used for digital encryption of SAML messages. Public key will be included in the metadata. 110 | | 111 |||||||||||||||||||
114 | |
115 | |
121 | ||||||||||||||||||
124 | |
125 |
126 | Security profile determines how is trust of digital signatures handled:
127 |
|
145 | ||||||||||||||||||
148 | |
149 | |
155 | ||||||||||||||||||
158 | |
159 |
160 | SSL/TLS Security profile determines how is trust of peer's SSL/TLS certificate (e.g. during Artifact
161 | resolution) handled:
162 |
|
178 | ||||||||||||||||||
181 | |
182 | |
191 | ||||||||||||||||||
194 | | 195 | Algorithm for verification of match between hostname in URL and hostname in the presented certificate. 196 | 197 | | 198 |||||||||||||||||||
201 | |
202 | |
208 | ||||||||||||||||||
211 | | 212 | Key used to authenticate this instance for SSL/TLS connections. 213 | | 214 |||||||||||||||||||
217 | |
218 | |
224 | ||||||||||||||||||
227 | | 228 | If true the generated metadata will be digitally signed using the specified signature key. 229 | 230 | | 231 |||||||||||||||||||
234 | |
235 | |
238 | ||||||||||||||||||
241 | | 242 | Algorithm used for creation of digital signature on metadata. Typical values are 243 | "http://www.w3.org/2000/09/xmldsig#rsa-sha1", 244 | "http://www.w3.org/2001/04/xmldsig-more#rsa-sha256" and "http://www.w3.org/2001/04/xmldsig-more#rsa-sha512" 245 | 246 | | 247 |||||||||||||||||||
250 | |
251 | |
257 | ||||||||||||||||||
260 | |
261 | |
267 | ||||||||||||||||||
270 | |
271 | |
277 | ||||||||||||||||||
280 | |
281 | |
287 | ||||||||||||||||||
290 | |
291 | |
297 | ||||||||||||||||||
300 | |
301 |
|
347 | ||||||||||||||||||
350 | |
351 |
|
380 | ||||||||||||||||||
383 | |
384 | |
390 | ||||||||||||||||||
393 | | 394 | 395 | Discovery 396 | profile enables service provider to determine which identity provider should be used 397 | for a particular user. Spring Security SAML contains it's own discovery service which presents 398 | user with an IDP list to select from. 399 | 400 | | 401 |||||||||||||||||||
404 | |
405 | |
408 | ||||||||||||||||||
411 | | 412 | When not set local IDP discovery URL is automatically generated when IDP discovery is enabled. 413 | | 414 |||||||||||||||||||
417 | |
418 | |
424 | ||||||||||||||||||
427 | 428 | 429 | |
430 |
Overview of all configured metadata for local service providers and remote identity providers.
15 |
17 | Default local service provider:
18 |
24 | Default service provider is available without selection of alias.
25 |
27 | Service providers:
28 |
31 |
35 | Identity providers:
36 |
39 |
43 | Metadata providers:
44 |
47 |
Detail of a single entity imported to Spring SAML's MetadataManager.
16 |Local entity: | 22 ||
Entity ID: | 26 ||
Entity alias: | 31 ||
Signing key: | 35 ||
Encryption key: | 39 ||
44 | 45 | 46 | |
47 | |
51 | 52 | 54 | |
55 | |
58 | In order to permanently store the metadata follow these instructions:
59 |
|
65 |
An error occurred.
19 |<% 32 | StringWriter stringWriter = new StringWriter(); 33 | PrintWriter printWriter = new PrintWriter(stringWriter); 34 | exception.printStackTrace(printWriter); 35 | out.println(stringWriter); 36 | printWriter.close(); 37 | stringWriter.close(); 38 | %>
Overview of the authenticated user's data.
21 |30 |
General information |
33 | |
Name: | 36 |
|
37 |
Principal: | 40 |
|
41 |
Name ID: | 44 |
|
45 |
Name ID format: | 48 |
|
49 |
IDP: | 52 |
|
53 |
Assertion issue time: | 56 |
60 |
Principal's SAML attributes |
63 | ||
> 67 | |
70 | |
74 | > 75 | <% 76 | Attribute a = (Attribute) pageContext.getAttribute("attribute"); 77 | String[] attributeValues = credential.getAttributeAsStringArray(a.getName()); 78 | pageContext.setAttribute("attributeValues", attributeValues); 79 | %> 80 | 81 | |
90 |
Subject confirmation |
93 | |
Method: | 96 ||
In response to: | 101 |
|
103 |
Not on or after: | 106 ||
Recipient: | 111 |
112 |
113 | |
115 |
118 |
Authentication statement |
121 | |
Authentication instance: | 124 ||
Session validity: | 129 ||
Authentication context class: | 134 |
|
136 |
Session index: | 139 ||
Subject locality: | 144 |
149 |
Conditions |
152 | |
Not before: | 155 ||
Not on or after: | 159 ||
Audience restriction: | 164 |
165 |
166 |
171 | |
172 |
175 |
Assertion XML |
178 |
181 |
|
183 |