Saml 2.0 元数据
解析<saml2:IDPSSODescriptor>
元数据
您可以解析断言方的元数据用RelyingPartyRegistrations
.
使用 OpenSAML 供应商支持时,生成的AssertingPartyMetadata
将为OpenSamlAssertingPartyDetails
.
这意味着您将能够通过执行以下作来获取底层 OpenSAML XMLObject:
-
Java
-
Kotlin
OpenSamlAssertingPartyDetails details = (OpenSamlAssertingPartyDetails)
registration.getAssertingPartyMetadata();
EntityDescriptor openSamlEntityDescriptor = details.getEntityDescriptor();
val details: OpenSamlAssertingPartyDetails =
registration.getAssertingPartyMetadata() as OpenSamlAssertingPartyDetails
val openSamlEntityDescriptor: EntityDescriptor = details.getEntityDescriptor()
用AssertingPartyMetadataRepository
您也可以比RelyingPartyRegistrations
通过使用AssertingPartyMetadataRepository
,一个只允许检索断言方元数据的接口。
这允许三个有价值的功能:
-
实现可以以过期感知方式刷新断言方元数据
-
的实现
RelyingPartyRegistrationRepository
可以更轻松地阐明依赖方与其一个或多个相应的断言方之间的关系 -
实现可以验证元数据签名
例如OpenSaml4AssertingPartyMetadataRepository
使用 OpenSAML 的MetadataResolver
和 API,其实现定期以过期感知方式刷新底层元数据。
这意味着您现在可以创建一个可刷新的RelyingPartyRegistrationRepository
只需几行代码:
-
Java
-
Kotlin
@Component
public class RefreshableRelyingPartyRegistrationRepository
implements IterableRelyingPartyRegistrationRepository {
private final AssertingPartyMetadataRepository metadata =
OpenSamlAssertingPartyMetadataRepository
.fromTrustedMetadataLocation("https://idp.example.org/metadata").build();
@Override
public RelyingPartyRegistration findByRegistrationId(String registrationId) {
AssertingPartyMetadata metadata = this.metadata.findByEntityId(registrationId);
if (metadata == null) {
return null;
}
return applyRelyingParty(metadata);
}
@Override
public Iterator<RelyingPartyRegistration> iterator() {
return StreamSupport.stream(this.metadata.spliterator(), false)
.map(this::applyRelyingParty).iterator();
}
private RelyingPartyRegistration applyRelyingParty(AssertingPartyMetadata metadata) {
return RelyingPartyRegistration.withAssertingPartyMetadata(metadata)
// apply any relying party configuration
.build();
}
}
@Component
class RefreshableRelyingPartyRegistrationRepository : IterableRelyingPartyRegistrationRepository {
private val metadata: AssertingPartyMetadataRepository =
OpenSamlAssertingPartyMetadataRepository.fromTrustedMetadataLocation(
"https://idp.example.org/metadata").build()
fun findByRegistrationId(registrationId:String?): RelyingPartyRegistration {
val metadata = this.metadata.findByEntityId(registrationId)
if (metadata == null) {
return null
}
return applyRelyingParty(metadata)
}
fun iterator(): Iterator<RelyingPartyRegistration> {
return StreamSupport.stream(this.metadata.spliterator(), false)
.map(this::applyRelyingParty).iterator()
}
private fun applyRelyingParty(metadata: AssertingPartyMetadata): RelyingPartyRegistration {
val details: AssertingPartyMetadata = metadata as AssertingPartyMetadata
return RelyingPartyRegistration.withAssertingPartyMetadata(details)
// apply any relying party configuration
.build()
}
}
OpenSaml4AssertingPartyMetadataRepository 还附带了一个构造函数,因此您可以提供自定义MetadataResolver .由于底层的MetadataResolver 正在执行过期和刷新,如果您直接使用构造函数,则只能通过提供执行此作的实现来获得这些功能。 |
验证元数据签名
您还可以使用OpenSaml4AssertingPartyMetadataRepository
通过提供适当的Saml2X509Credential
s 中执行如下作:
-
Java
-
Kotlin
OpenSamlAssertingPartyMetadataRepository.withMetadataLocation("https://idp.example.org/metadata")
.verificationCredentials((c) -> c.add(myVerificationCredential))
.build();
OpenSamlAssertingPartyMetadataRepository.withMetadataLocation("https://idp.example.org/metadata")
.verificationCredentials({ c : Collection<Saml2X509Credential> ->
c.add(myVerificationCredential) })
.build()
如果未提供凭据,则组件将不会执行签名验证。 |
生产<saml2:SPSSODescriptor>
元数据
您可以使用saml2Metadata
DSL 方法,如下所示:
-
Java
-
Kotlin
http
// ...
.saml2Login(withDefaults())
.saml2Metadata(withDefaults());
http {
//...
saml2Login { }
saml2Metadata { }
}
您可以使用此元数据终端节点向断言方注册您的信赖方。 这通常就像找到正确的表单字段来提供元数据端点一样简单。
默认情况下,元数据端点为/saml2/metadata
,尽管它也响应/saml2/metadata/{registrationId}
和/saml2/service-provider-metadata/{registrationId}
.
您可以通过调用metadataUrl
方法:
-
Java
-
Kotlin
.saml2Metadata((saml2) -> saml2.metadataUrl("/saml/metadata"))
saml2Metadata {
metadataUrl = "/saml/metadata"
}
改变方式RelyingPartyRegistration
被查找
如果你有不同的策略来确定哪个RelyingPartyRegistration
要使用,您可以配置自己的Saml2MetadataResponseResolver
如下所示:
-
Java
-
Kotlin
@Bean
Saml2MetadataResponseResolver metadataResponseResolver(RelyingPartyRegistrationRepository registrations) {
RequestMatcherMetadataResponseResolver metadata = new RequestMatcherMetadataResponseResolver(
(id) -> registrations.findByRegistrationId("relying-party"));
metadata.setMetadataFilename("metadata.xml");
return metadata;
}
@Bean
fun metadataResponseResolver(val registrations: RelyingPartyRegistrationRepository): Saml2MetadataResponseResolver {
val metadata = new RequestMatcherMetadataResponseResolver(
id: String -> registrations.findByRegistrationId("relying-party"))
metadata.setMetadataFilename("metadata.xml")
return metadata
}