If we are to implement a project with a Tupas Authentication on behalf of a customer, I am quite sure that they will ask us about the meaning of this warning on the project's page:

This project is not covered by Drupal’s security advisory policy.

I think it will be hard to convince a customer to use this project before a full release. Would appreciate it if we could get information about the 1.0 timeline and what are the current blockers; is there anything we could do as part of a potential project to help bring the project forward?

Comments

badrange created an issue. See original summary.

badrange’s picture

badrange commented
Issue summary: View changes
tuutti’s picture

tuutti commented

Sorry for the late response.

The reason why I haven't published 8.x-1.0 release is because I recently changed employer and I'm no longer working with any projects using this module.

I don't really have any roadmap for 1.0 release, but here's list of @todo comments in the code. Most of them are not necessary relevant anymore but would be nice to fix them or remove the @todo comment:

modules/tupas_registration/src/UniqueUsername.php:46:      // @todo Generate human readable username?
modules/tupas_registration/src/Form/RegisterForm.php:95:    // @todo Should we respect account verification setting?
modules/tupas_session/tupas_session.routing.yml:19:  # @todo Review this. We need to generate unique transaction id for every page request.
modules/tupas_session/src/TupasTransactionManager.php:46:    // @todo This might cause some issues with logged in users.
modules/tupas_session/src/TupasSessionManager.php:71:   * @todo Replace with time service in 8.3.x.
modules/tupas_session/src/TupasSessionManager.php:115:   * @todo Refactor.
badrange’s picture

badrange commented

Thanks for getting back on this! Good to know that the module is in use in production systems, at least.

I wonder what it would take for this one to get a full release; would it make sense to add a new maintainer? It could be someone from your previous employer (since they are actually using it) or from another company.

tuutti’s picture

tuutti commented
Status: Active » Fixed
badrange’s picture

badrange commented

🏆

Thank you! Now this module is also covered by the security team!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.