public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Mark D. Baushke" <mdb@gnu.org>
To: Frank Cohen <fcohen@pushtotest.com>
Cc: help-gnats@gnu.org
Subject: Re: Guest view priviledges?
Date: Sun, 12 Oct 2003 16:28:00 -0000	[thread overview]
Message-ID: <13781.1065975998@juniper.net> (raw)
In-Reply-To: Mail from Frank Cohen <fcohen@pushtotest.com>  dated Sun, 12 Oct 2003 07:40:51 PDT <13F206F8-FCC2-11D7-8A32-003065534A54@pushtotest.com>

Frank Cohen <fcohen@pushtotest.com> writes:

> I've posted this twice before with no answer. Would someone please
> respond. Is there a way to enable Gnatsweb to let guest (ie - users
> that have no signed-on) to view a bug db? If so, how?

First, you need to deal with your website authentication (or not) to
allow a guest account.

Second, you need to provide a gnatsd.access file with a guest account
with some known password (empty passwords should also be possible) that
is given view privilege.

An entry like this:

guest:$0$guest:view:default

in your gnatsd.user_access file should mean that a loging with userid
'guest' and password 'guest' should get the view access you want. Be
aware that you would want to place this near the top of the file before
any wild-card login entries.

For more information, you may wish to look at google with
a search string like

  view guest gnats site:mail.gnu.org

There have been various threads and bug reports over the last few years
on this topic.

	Good luck,
	-- Mark


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2003-10-12 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-12 14:44 Frank Cohen
2003-10-12 16:28 ` Mark D. Baushke [this message]
2003-10-12 17:02   ` Frank Cohen

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=13781.1065975998@juniper.net \
    --to=mdb@gnu.org \
    --cc=fcohen@pushtotest.com \
    --cc=help-gnats@gnu.org \
    /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).