Re: WEB DB: Problem granting priveleges other than 'Public"

[Quoted] Create a database access descriptor DAD (e.g.: toall) and specify *both* user and password for that dad (e.g. scott/tiger). Grant execute privileges [Quoted] for menu and reports to scott. Call the components (e.g. menu publicmenu) using the dad toall in the url, e.g.:
http://myserver/toall/scott.publicmenu.show. There's no need for login, cause webdb can dad toall resolve as login as scott/tiger and invoking package publicmenu Procedure show in the scott-schema.

If you want a login from the user take a DAD without predefined user/password -> user must login -> to see his components he must have been [Quoted] granted execute privileges. By the way: Grant privileges to roles, not to users, and grant that roles to the user - makes maintenance a lot more easier.

Hth

Klaus

"Nick Yeast" <nospam_at_bigfoot.com> schrieb im Newsbeitrag news:lr6smsgcvco890rd2fo03cmbf5vbru5fjl_at_4ax.com...
> I have created a WebDB site and added some content (a menu with a few
> reports). If I set all priveleges to 'Public', users can use the
> components. However, if I set either the execute priveleges or the
> menu item priveleges to anything other than 'Public' no users can
> either see or successfully execute them, even if the user is
> specifically granted permission to view the menu or execute the
> component.
>
> This is holding true for me both for priveleges specifically granted
> to the user, or for priveleges granted via a role. I need to be able
> to make certain website content available to the public and restrict
> other content to one or more groups.
>
> What am I missing here? Can anyone assist?
>
> Thanks much in advance!!
> --------
> Nick Yeast
> replace 'nospam' with 'club11'
Received on Thu Jul 13 2000 - 00:00:00 CEST