Re: [Geoserver-users] geoserver/saml/metadata endpoint

[Alessandro F. <ale...@gm...>]

Thank you very much for the reply, Andrea.  SAML integration is a fairly
integration requirement for the successful adoption of GeoServer in our
enterprise, so I will happily delve into the source code to better
understand it.  I've done SAML work with Spring Security in the past with
various projects, so I'd be happy to dig into this module.

Regards,
Alessandro

On Wed, Aug 25, 2021, 9:23 AM Andrea Aime <and...@ge...>
wrote:

> Alessandro,
> the module is a "community module
> <https://docs.geoserver.org/master/en/user/community/index.html>", which
> among other things, means there is no appointed maintainer.
>
> Looking at the short module history
> <https://github.com/geoserver/geoserver/commits/main/src/community/saml/src/main>,
> there are only two commits that are actually relevant to the modules
> (the other two are general housekeeping), and they are from two italian
> developers... and it's August :-D
>
> For this module, I believe your choices are either to delve into its code
> yourself, or look for a commercial <http://geoserver.org/support/>
> support provider that can help <http://geoserver.org/support/>. If enough
> business starts rolling around the module, there are good chances
> it might become an officially supported module down the road.
>
> Cheers
> Andrea
>
>
> On Wed, Aug 25, 2021 at 3:10 PM Alessandro Ferrucci <
> ale...@gm...> wrote:
>
>> Hello -
>>
>> Just wondering if anyone has any insight into this?
>>
>> Thank you
>>
>> On Mon, Aug 23, 2021 at 10:24 PM Alessandro Ferrucci <
>> ale...@gm...> wrote:
>>
>>> Hello -
>>>
>>> Normally when developing Spring SAML SP's, Spring creates an endpoint
>>> that outputs the SP's metadata XML under <context_root>/saml/metadata.  I
>>> have configured the SAMLv2 filter but when I attempt to hit
>>> geoserver/saml/metadata, I receive a 404. Is the SAML filter not programmed
>>> to expose the saml/metadata endpoint?
>>>
>>> thank you,
>>> Alessandro
>>>
>>
>>
>> --
>> Signed,
>> Alessandro Ferrucci
>> _______________________________________________
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>