@@ -47,8 +47,8 @@ private RelyingPartyRegistrations() {
47
47
* Return a {@link RelyingPartyRegistration.Builder} based off of the given SAML 2.0
48
48
* Asserting Party (IDP) metadata location.
49
49
*
50
- * Valid locations can be classpath- or file-based or they can be HTTP endpoints. Some
51
- * valid endpoints might include:
50
+ * Valid locations can be classpath- or file-based or they can be HTTPS endpoints.
51
+ * Some valid endpoints might include:
52
52
*
53
53
* <pre>
54
54
* metadataLocation = "classpath:asserting-party-metadata.xml";
@@ -71,8 +71,8 @@ private RelyingPartyRegistrations() {
71
71
* about the asserting party. Thus, you will need to remember to still populate
72
72
* anything about the relying party, like any private keys the relying party will use
73
73
* for signing AuthnRequests.
74
- * @param metadataLocation The classpath- or file-based locations or HTTP endpoints of
75
- * the asserting party metadata file
74
+ * @param metadataLocation The classpath- or file-based locations or HTTPS endpoints
75
+ * of the asserting party metadata file
76
76
* @return the {@link RelyingPartyRegistration.Builder} for further configuration
77
77
*/
78
78
public static RelyingPartyRegistration .Builder fromMetadataLocation (String metadataLocation ) {
@@ -132,8 +132,8 @@ public static RelyingPartyRegistration.Builder fromMetadata(InputStream source)
132
132
* Return a {@link Collection} of {@link RelyingPartyRegistration.Builder}s based off
133
133
* of the given SAML 2.0 Asserting Party (IDP) metadata location.
134
134
*
135
- * Valid locations can be classpath- or file-based or they can be HTTP endpoints. Some
136
- * valid endpoints might include:
135
+ * Valid locations can be classpath- or file-based or they can be HTTPS endpoints.
136
+ * Some valid endpoints might include:
137
137
*
138
138
* <pre>
139
139
* metadataLocation = "classpath:asserting-party-metadata.xml";
@@ -157,7 +157,7 @@ public static RelyingPartyRegistration.Builder fromMetadata(InputStream source)
157
157
* about the asserting party. Thus, you will need to remember to still populate
158
158
* anything about the relying party, like any private keys the relying party will use
159
159
* for signing AuthnRequests.
160
- * @param location The classpath- or file-based locations or HTTP endpoints of the
160
+ * @param location The classpath- or file-based locations or HTTPS endpoints of the
161
161
* asserting party metadata file
162
162
* @return the {@link Collection} of {@link RelyingPartyRegistration.Builder}s for
163
163
* further configuration
0 commit comments