Skip to content
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.

Missing configurable AttributeConsumingService in Metadata Generator #437

Open
impos89 opened this issue May 17, 2019 · 2 comments
Open

Comments

@impos89
Copy link

impos89 commented May 17, 2019

Hi,
As I see, now it's not possible to configure md:AttributeConsumingService in MetadataGenerator for service provider.
Is it possible to do it in other way without overriding MetadataGenerator implementation ?

If it's missing, I can add support for that and share with pull request.

An example of expected result in sp metadata file:
<md:AttributeConsumingService index="1"> <md:ServiceName xml:lang="it">Nome del servizio</md:ServiceName> <md:ServiceDescription xml:lang="it">Descrizione del servizio</md:ServiceDescription> <md:RequestedAttribute Name="email" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic"/> <md:RequestedAttribute Name="name" </md:AttributeConsumingService>

@fhanik
Copy link
Contributor

fhanik commented Jul 8, 2019

Yes, a PR is greatly appreciated. Currently md:AttributeConsumingService is left out because the endpoint for that is not implemented.

@issilin
Copy link

issilin commented Sep 21, 2019

@fhanik Hello! Is this task still relevant?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants