From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: S Ramesh <rashanmu@npd.hcltech.com>
Cc: gnats-devel@sources.redhat.com, bugs <bug-gnats@gnu.org>
Subject: Re: Gnatsweb help
Date: Wed, 25 Jul 2001 15:48:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20010726003616.00a3a9b0@10.10.1.1> (raw)
In-Reply-To: <3B5BCED4.5FCDCAC3@npd.hcltech.com>
At 12:44 23.07.01 +0530, S Ramesh wrote:
>I have installed gnats 3.113.1 and gnatsweb 2.8.2 in a server. now i have
>done with instaalation.. i could able to send and edit PR from web. but the
>problem is how to configure it.
>
>1. i gnatsd.access i have a username and passwd for a user with accessleve
>and dbase alias name. now when a user creates a PR his reporters mail id
>field is filled by him and he can give any email id. how to restrict this
>stuff. is there any possiblity of having unix username and passwd
>associated with gnatsd.access user name and passwd.
In gnatsweb.pl, you could remove the field from the form and instead have
it sent with the form as a hidden value. The modification should be fairly
straightforward if you know a little bit about HTML forms.
>2. once logged in thru web from a browser froma machine the last login
>remains even if we kill the browser. so once logged in the cookies get
>enables. how to make it to ask every time for username and passwd.
One way would of course be to run an OS where cookies are kept private to
each user. However, I will probably add a "logout" button to the main page
shortly. This will clear the current login cookie and leave you at the
login screen afterwards. I'll just have to reach a conclusion in a debate
with myself over whether the Login Again button should simply have its name
changed and behaviour slightly modified, or whether we need an all-new button.
A logout button will definitely appear in Gnatsweb 4, but it should be easy
to port, so it will quite likely also appear in a new Gnatsweb 2.8.x release.
Yngve Svendsen
Gnatsweb maintainer
next prev parent reply other threads:[~2001-07-25 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 0:11 fix for PR 219 - large PRs or updates take many minutes to process Dirk Bergstrom
2001-07-23 0:26 ` Gnatsweb help S Ramesh
2001-07-25 15:48 ` Yngve Svendsen [this message]
2001-07-30 11:33 ` fix for PR 219 - large PRs or updates take many minutes to process Milan Zamazal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.2.20010726003616.00a3a9b0@10.10.1.1 \
--to=yngve.svendsen@clustra.com \
--cc=bug-gnats@gnu.org \
--cc=gnats-devel@sources.redhat.com \
--cc=rashanmu@npd.hcltech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).