This project is currently not under active development

[bzvestey]

Hello everyone, we here at OneLogin wanted to let you know that this project is currently not under active development. We apologize for recent silence and continued wait, but we intend to resume maintenance in the future.

Note that I am unable to make any more changes to this repository, and I don't have someone I can forward you to at this time.

[mauromol]

Two proposals from me:

1. may I become a committer to maintain this project, although on a voluntary basis and with no warranty at all with regards to time and features?
2. as an alternative, if I were to create a somewhat long term fork of this project, can I continue to use onelogin names in one or more of these locations:
   1. package names
   2. preferences names
   3. Maven artifact names (e.g. group id)
   4. anything else I cannot think of right now?

By the way, is @eriktalvi involved in this project any more?

[haavar]

@mauromol I would also be interested in taking over maintenance of this project. I was considering making a fork for my own purpose or maybe writing one from scratch that suits my needs, but neither one of those options are obviously not ideal.

Depending on onelogin's stand on this, we could start a new fork without any onelogin references. I don't think the migration for any clients using this would be too cumbersome.

I can commit a fair bit of time to this, as the alternative would pretty much mean writing my own.

[pitbulk]

Hi @mauromol,

Im also considering to fork all SAML repos and try at least to give them critical support/maintenance, not only the java-saml one.

I will try to contact someone at OneLogin to see if that gonna be possible.

[mrmoss]

Hi all - Engineer at OneLogin here. Starting the process to get these all transferred over to @pitbulk. Not sure how long it will take, but since they are already opensource, I don't see how they can be against it...

[mauromol]

Thanks for the news and thanks @pitbulk for stepping up. I hope the transition for this project will be quick.

[kleptog]

How's it going with the transfer? And does this include the rights to update the packages on PyPi?

[eriktalvi]

Development Update. OneLogin is releasing these projects to a new organization with @pitbulk. This migration is actively happening and the priority is to make the transition as seamless as possible for end users of these repo/packages.

We expect that there are several questions that you all have and we are working with @pitbulk to answer those in our next update. Below are some answers we have for you now.

What is being changed?
The repos/packages will no longer be officially supported and hosted by OneLogin. This means that they will not be in the OneLogin Github org but in a new org, SAML Tools. References to the repos being provided and supported by OneLogin Inc will be removed.

Which projects are being moved?
All SAML repos will be moved. This includes: java-saml, python3-saml, wordpress-saml, moodle-saml, joomla-saml, drupal-saml, and dotnet-saml

When will this transfer happen?
We expect this to be completed by the end of the year, Dec 31 2022.

Why is this transfer happening?
OneLogin is releasing control of these open source repos so that these repos can maintained by community instead.

When will the next update be?
To keep you all informed of status, we will give monthly updates of how the transfer is proceeding.