Issue 2550764
Created on 2012-07-03 06:07 by DanielGrimwood, last changed 2024-10-20 22:52 by rouilj.
msg4588 |
Author: [hidden] (DanielGrimwood) |
Date: 2012-07-03 06:07 |
|
Roundup works nicely with Apache's "AuthType Basic" passing through the
REMOTE_USER to roundup. Our web interface is not anonymously available;
users must have a LDAP account. Under this setup we prefer to have the
Login box and Logout link not appear at all as they just confuse users.
Currently I edit html/page.html and comment out the Login form and
Logout link. It would be more elegant and upgrade-friendly if this
could be done via a flag in config.ini rather than editing the html
file. It's easy enough to edit the html file, but others might find the
feature useful too.
|
msg4589 |
Author: [hidden] (ber) |
Date: 2012-07-03 06:44 |
|
Hi Daniel,
thanks for your suggestion!
Ideally you or someone else creates a patch for this behaviour.
I guess this would lead to some conditional in the page template.
It is hard to guess how many people are interested in having this
feature as option. If we believe it is a significant fraction,
it certainly makes sense to add it.
|
msg5652 |
Author: [hidden] (rouilj) |
Date: 2016-06-27 03:27 |
|
I don't think we need a new flag in config.ini, we should just be able
to reuse the WEB_HTTP_AUTH configuration option right?
|
msg6637 |
Author: [hidden] (rouilj) |
Date: 2019-09-14 14:15 |
|
It should be possible to have local as well as http auth users. So this
probably needs a separate setting, or http_auth is modified to yes, no,
both (implying local auth and http auth).
But given other auth methods (openid, github) could be supported,
I wonder if this should just be an edit if page.html and documented
in wiki/customizing.html.
|
msg8143 |
Author: [hidden] (rouilj) |
Date: 2024-10-20 22:52 |
|
I agree this would be more upgrade friendly for people who haven't customized
the page.html template. However, one of the reasons people choose Roundup is
the ability to change the templates to suite their site.
So upgrading templates is often going to require pick/choose/merge from the
upgrading document rather than copying a newly distributed file into a running
tracker.
We recommend (but don't document the workflow anywhere 8-() using a version control
system that can be used to automate the merge when new versions come out. I use Fossil
with a vendor branch to simplify the merge, some may use git or even rcs 8-).
As a result I am going to close this as won't fix.
Daniel if you're still out there I hope you enjoy/enjoyed using Roundup.
-- rouilj
|
|
Date |
User |
Action |
Args |
2024-10-20 22:52:02 | rouilj | set | status: new -> closed resolution: wont fix messages:
+ msg8143 |
2019-09-14 14:15:58 | rouilj | set | messages:
+ msg6637 |
2016-07-13 01:01:48 | rouilj | set | assignee: rouilj |
2016-06-27 03:27:42 | rouilj | set | nosy:
+ rouilj messages:
+ msg5652 |
2012-07-03 06:44:37 | ber | set | nosy:
+ ber messages:
+ msg4589 |
2012-07-03 06:07:40 | DanielGrimwood | create | |
|