Hi Aaron Taking this to the list...
> That makes sense. I was thinking something like checking for > "overrideTemplate" before getting the default one but storing in the repo > would be good. My only possible issue with that is setting up a new one the > first time sling starts up would be annoying (unless there is some way to > push things into the repo on startup?). If there is no way to push things > into the repo on startup I would recommend doing something like allowing a > bundle fragment to control this. Things can be injected into the repository on startup using the initial content feature, which is described at [1]. I could then imagine, that the httpauth bundle just installs the default template using the initial content feature, but in a way, that any existing file is not replaced. This file may then be edited or replaced by other files either in place or by another bundle providing initial content. Regards Felix [1] http://cwiki.apache.org/SLINGxSITE/content-loading.html > >> Adapt the Http Authenticator to the refined authentication process >> ------------------------------------------------------------------ >> >> Key: SLING-939 >> URL: https://issues.apache.org/jira/browse/SLING-939 >> Project: Sling >> Issue Type: Sub-task >> Components: Extensions >> Affects Versions: Extensions httpauth 2.0.2 >> Reporter: Felix Meschberger >> Assignee: Felix Meschberger >> >> Adapt the HTTP Header authentication handler to the new refined >> authenticaiton initiation processing implemented by SLING-938. >> Tasks: >> * The LoginServlet calls the new requestAuthentication service method >> * requestAuthentication method will now draw the login form >
