What are the challenges you face when working across database platforms? Take the survey

Public Read Only Access

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited March 17, 2004 8:43AM in Aardvark
Hi Scott,

That's a tough one to answer. Obviously, you don't want your external
users to have the ability to edit an open issue, and there's a possibility
that there are issues open for internal products that you don't want them to
see. Bug.asp and Bugs.asp will require a user to log in or they won't work
properly. That pretty much leaves the knowledge base as the only
publicly-available source of information that an external user can't tamper

The only way that this is going to work is if you 'roll your own'
ASP/ADO solution to allow a crude search and display of a recordset of
matching bugs to the external user.


Brian Donahue
Red Gate Software Ltd

"Scott Willhite" <mrswoop@tough.net> wrote in message
> Looking for one more enabler. We'd like to basically allow read-only
> (and search) to the entire bug list. Mostly, to allow anonymous
> to verify that they are not duplicating something already reported. What
> would you recommend as the best way to do this? I've tried using the kb
> articles, but this means manually setting every submission as an
> is there another way to do this? I also tried setting up a guest ID, but
> seems that some of the permissions limitations are not quite working...
> so I don't feel confident allowing an anonymous login either.
> Ideas?
This discussion has been closed.