From: "Eicke Felipe" <eickeaf@hotmail.com>
To: Priya.Nayar@fci.com
Cc: help-gnats@gnu.org
Subject: RE: Autentication Again...
Date: Thu, 05 Jun 2003 12:36:00 -0000 [thread overview]
Message-ID: <BAY8-F27ymfN8jYd1bn00006869@hotmail.com> (raw)
Hi Priya
I follow your instructions but when I tried to access gnatsweb the following
error message appears:
Login
Return code: 422 - Access denied (login again & check usercode/password)
Another question...In your environment when the user priya log she only edit
her pr's and sees others?
Could you help me?
Regards.
Eicke.
>From: "Nayar, Priya G" <Priya.Nayar@fci.com>
>To: 'Eicke Felipe' <eickeaf@hotmail.com>, help-gnats@gnu.org
>Subject: RE: Autentication Again...
>Date: Thu, 5 Jun 2003 11:11:43 +0530
>
>in the file gnatsd.access in the following path(it depends on where u hv
>installed, and compiles ur sources for gnats...)
>
>
>[gnats@idc_linux_bld01 gnats]$ pwd
>/home/gnats
>[gnats@idc_linux_bld01 gnats]$ ls
>dead.letter ginstall.sh gnats-3.999.1.tar gnatsscripts
>gnatsweb.cgi.new support
>forceLogo.gif gnats-3.999.1 gnats-install gnatsweb.cgi mbox
>[gnats@idc_linux_bld01 gnats]$ cd gnats-install/
>[gnats@idc_linux_bld01 gnats-install]$ ls
>bin com etc info libexec man share
>[gnats@idc_linux_bld01 gnats-install]$ cd com/
>[gnats@idc_linux_bld01 com]$ ls
>dummyproj gnatsdb gnatstest library project1 project2 project3
>tester
>[gnats@idc_linux_bld01 com]$ cd dummyproj/
>[gnats@idc_linux_bld01 dummyproj]$ ls
>dummyproj documentation dummyproj firmware dummyproj hardware dummyproj
>software gnats-adm gnats-queue pending
>[gnats@idc_linux_bld01 dummyproj]$ cd gnats-adm/
>[gnats@idc_linux_bld01 gnats-adm]$ ls
>addresses categories classes current dbconfig gnatsd.access index
>locks responsible states submitters
>[gnats@idc_linux_bld01 gnats-adm]$ vi gnatsd.access
>#
># User access levels with the GNATS daemon.
>#
># Any line which begins with a `#' is considered a comment, and GNATS
># will ignore it.
>#
># Each entry has the format:
>#
># userid:password:access-level:database-alias
>#
># Wildcard characters are supported for userid, password and
>database.
># "*" matches anything; "?" matches any single character
>#
># * userid: a user id to gain access to gnatsd
># * password: a password for the user. Passwords prefixed by $0$ are
># assumed to be plain-text. Passwords without a prefix are
># assumed to be encrypted with standard crypt(), while
>passwords
># prefixed with $1$ are assumed to be MD5 encrypted.
># MD5 and crypt() encryption may not be available on all
>systems.
># * access-level: (default = edit)
># deny - gnatsd closes the connection
># none - no further access until userid and password
>given
># listdb - same as 'none', except that the user is allowed
>to
># list the available databases on the server
># view - query and view PRs with Confidential=no only
># viewconf - query and view PRs with Confidential=yes
># edit - full edit access
># admin - full admin access (required for operations such
>as
># deleting PRs)
># This overrides (increases but never lowers) the access level
>given
># as the default for the user's host in the global gnatsd.conf
>file.
># * database-alias: a comma-separated list of database names.
># It's ignored in gnatsd-adm/gnatsd.access since this file is
>already
># database specific.
>#
>#*:*:view:
>priya:password:edit:
>bjuda:password:edit:
>~
>
>
>
>set the access levels for different users as view, edit or admin(all
>privileges). this file exists for each & every project in the database. u
>can set different people to hv differet access levels for different
>projects.
>in file shown to u for ref, users priya & bjuda hv edit access.
>
>
>~
>~
>~
>~
>~
>~
>~
>~
>~
>~
>~
>~
>"gnatsd.access" 38L, 1823C
>
>
>hope this helps & answers ur question.
>:-)
>
>rgds,
>priya
>
>-----Original Message-----
>From: Eicke Felipe [mailto:eickeaf@hotmail.com]
>Sent: Thursday, June 05, 2003 12:29 AM
>To: help-gnats@gnu.org
>Subject: Autentication Again...
>
>
>Hi folks...
>I installed Gnatsweb v3.99.3 and Gnats v4.0-beta1. Everything is functional
>but I need to control the access by user. When the user X that have a
>password logs in gnastsweb only control your tasks and see anothers belong
>to others users. Is There a way to configure this environment?
>Today any user get access into gnatsweb no password, this is very
>dangerous...I need help.
>
>Thanks and regards.
>Eicke.
>
>_________________________________________________________________
>Help STOP SPAM with the new MSN 8 and get 2 months FREE*
>http://join.msn.com/?page=features/junkmail
>
>
>
>_______________________________________________
>Help-gnats mailing list
>Help-gnats@gnu.org
>http://mail.gnu.org/mailman/listinfo/help-gnats
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2003-06-05 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 12:36 Eicke Felipe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 5:48 Nayar, Priya G
2003-06-04 19:04 Eicke Felipe
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=BAY8-F27ymfN8jYd1bn00006869@hotmail.com \
--to=eickeaf@hotmail.com \
--cc=Priya.Nayar@fci.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).