Closed (duplicate)
Project:
Drupal 8 Contrib Porting Tracker
Version:
8.x-0.x-dev
Component:
Module
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2015 at 04:17 UTC
Updated:
8 Dec 2021 at 00:34 UTC
Jump to comment: Most recent
Comments
Comment #2
mgiffordComment #3
suthagar commentedComment #4
suthagar commentedComment #5
suthagar commentedComment #6
suthagar commentedComment #7
gábor hojtsy@suthagar: I see you started a port on your own initiative. It is not clear if your port follows the doc set up with suggestions, neither your availability and plans. Also given your own sandbox, what is your plan of collaboration with others? what is the plan to get it back to the official repo? You also posted a completion date that is in the past now (and was 5 days after you pushed your first commit which was not followed by other commits). How are things? Should someone else take this over? I can help.
Comment #8
gábor hojtsyDue to lack of response, I took over the process and it is now at https://www.drupal.org/sandbox/goba/2632462
Comment #9
mgiffordComment #10
mgifford@Gabor's working on it here https://www.drupal.org/sandbox/goba/2632462
Comment #11
gábor hojtsyProgressing well at https://www.drupal.org/sandbox/goba/2632462, HTTPS detection and path/role based redirection works.
Comment #12
nerdsteinWe had some high level discussions about porting this module. We have a little bit of code to show for it, and some issues we captured.
Due to time constraints, it doesn't look like anyone's able to pick this back up or pitch in with the efforts in the other repository.
Found here: https://github.com/d8-contrib-modules/securepages
Comment #13
kmoll commented@Gabor @nerdstein I am interested in collaborating on this and seeing this ported to a stable release. Is seems https://www.drupal.org/sandbox/goba/2632462 is the current version that is being worked on. Can I get confirmation of this.
Comment #14
chris mcgrath commentedI would also be interested in assisting however possible.
Comment #15
kmoll commentedGreat @Chris McGrath. I've spoken to @nerdstein and @Gabor Hojtsy, and they have both done great work on this, but have lost time to be able to work on this. My plan is to use the port that Gabor has as it is the furthest along. I will go through it again and figure out exactly where we are and what needs to be done to get it ported and create a new road map and tickets for it. Then we can take a look and start in on it. Let me know what you think.
Comment #16
kmoll commentedI have been testing the port and other than a few bugs, which there are issues for, I think this can be used as the official version of the module and we should create an 8.x-1.x-dev branch on the main module for this so that development work can continue there.
Comment #17
kmoll commentedFor anyone else that wants to pick this up, we've decided against using the module in favor of using https everywhere.
Comment #18
mfbHTTPS everywhere is almost always the best choice :D
But for sites that are available via both HTTP and HTTPS Secure login module is available.
Comment #19
mmjvb commentedWith only dev release Status should be Needs work.
Comment #20
drummThe security tag is for tracking public security issues on projects that do not fall under the security advisory coverage policy, and security hardening issues.
Comment #21
wim leers#3252415: Create securepages to securelogin migration is adding an automatic migration path from
securepagestosecurelogin, which per #18 is preferable nowadays anyway. (Plus,securepageshas no D8|D9 port.)Going to be a little bit bold and mark this . Because it can help the remaining ~10K D7 sites using
securepagesmigrate to D8|9 😊Comment #22
mfbIt might be helpful to better document this w/ a link from Secure Pages to Secure Login, see proposal @ #3253190: Add a link to Secure Login module on Secure Pages module page