Hi, Currently org-apache-sling-auth-saml2 build runs about 65 seconds on my local workstation, and several minuted in the Jenkins CI pipeline. My understanding is that projects in the Sling Whiteboard repo should be moved to another repo before releasing to Maven Central.
Therefore, I'd like to create a new repo for the code currently living in the whiteboard at [0]. Proposed repository name: org-apache-sling-auth-saml2 Artifact id: org.apache.sling.auth.saml2 The resulting jar file will be a java OSGi bundle that when configured is used to authenticate external users using SAML 2.0 protocols. The README [1] has more details on requirements, supported features and usage. Thoughts? Cris Rockwell Application Architect Senior University of Michigan | College of Literature, Science, and the Arts LSA Technology Services | Web & Application Development Services [0]: https://github.com/apache/sling-whiteboard/pull/69 [1]: https://github.com/apache/sling-whiteboard/tree/SLING-9397/update-removed-saml-config-service/saml-handler#readme
