10:33 a.m.
Works great, thank you.
Added –spit-fronted to start.sh inside container and then created new image.
/Ulrik
Från: Ivan Kanakarakis <ivan.kanak at gmail.com>
Skickat: den 19 augusti 2020 15:15
Till: Ulrik Åhlander <Ulrik.Ahlander at Xlent.Se>
Kopia: Scott Koranda <skoranda at gmail.com>; satosa-users at lists.sunet.se
Ämne: Re: [satosa-users] SAMLVirtualCoFrontend metadata
If you are using a container then probably the start.sh script is invoked.
If you are building your own image then modify it to include the --split-frontend option.
If you are using a pre-built image then override the every point to use again a modified
version of the start.sh script. (Using docker, use the --entrypoint option)
The start.sh script and the command that creates the metadata is here:
https://github.com/IdentityPython/SATOSA/blob/master/docker/start.sh#L35
That should change to
satosa-saml-metadata \
--split-frontend \
... # as it is in the script
I hope this helps.
Cheers,
On Wed, Aug 19, 2020, 15:43 Ulrik Åhlander <Ulrik.Ahlander at
xlent.se<mailto:Ulrik.Ahlander at xlent.se>> wrote:
Hello,
Great, so there i a function to split the metadata. But where to enter what?
saml2_virtualcofrontend.yaml ?
I use a Docker container and when I start the container metadata is produced
automatically.
/Ulrik
Från: Ivan Kanakarakis <ivan.kanak at gmail.com<mailto:ivan.kanak at
gmail.com>>
Skickat: den 19 augusti 2020 13:50
Till: Scott Koranda <skoranda at gmail.com<mailto:skoranda at gmail.com>>
Kopia: Ulrik Åhlander <Ulrik.Ahlander at Xlent.Se<mailto:Ulrik.Ahlander at
Xlent.Se>>; satosa-users at lists.sunet.se<mailto:satosa-users at
lists.sunet.se>
Ämne: Re: [satosa-users] SAMLVirtualCoFrontend metadata
Hello,
What command did you try to use to get the metadata files? You must use the
--split-frontend flag to get separate files.
Cheers,
On Wed, Aug 19, 2020, 14:10 Scott Koranda <skoranda at gmail.com<mailto:skoranda at
gmail.com>> wrote:
Hi,
I suspect this is a bug.
Can you please file an issue at
https://github.com/IdentityPython/SATOSA/issues
and I will try to take a look at it in the coming days?
Thanks,
Scott
Hi
I´m trying to setup SAMLVirtualCoFrontend with three entityIDs, but got a problem that I
hope someone knows about.
It seems as all three entityIDs are get up by SATOSA as I can see this in the log:
Created URL regex (^Saml2)/(Org1|Org2|Org3)/sso/post
Adding mapping ('(^Saml2)/(Org1|Org2|Org3)/sso/post'
Created URL regex (^Saml2)/(Org1|Org2|Org3)/sso/redirect
Adding mapping ('(^Saml2)/(Org1|Org2|Org3)/sso/redirect'
But the metadata frontend.xml only contains entityID for the last entry, in this case
"Org3".
The log shows that metadata is written three times to the same file, see log entry
below.
Writing metadata to '/cfg/metadata/frontend.xml'
Writing metadata to '/cfg/metadata/frontend.xml'
Writing metadata to '/cfg/metadata/frontend.xml'
Writing metadata to '/cfg/metadata/backend.xml'
Is there anything I can do to get correct frontend metadata for all three COs ?
A configuration item to get separate filenames or something?
I´m using latest Docker image satosa/satosa as of yesterday
/Ulrik Å
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se<mailto:satosa-users at lists.sunet.se>
https://lists.sunet.se/listinfo/satosa-users
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se<mailto:satosa-users at lists.sunet.se>
https://lists.sunet.se/listinfo/satosa-users