A user is able to edit the default enterprise database,

508
6
Jump to solution
09-25-2013 02:30 PM
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

A user is able to edit the default enterprise database,

I have the following scenario:

1. The enterprise geodatabase ???H??? is created with the Sa and sde

[ATTACH=CONFIG]27765[/ATTACH], [ATTACH=CONFIG]27766[/ATTACH]

2. u1 is created to be a user for the H database

[ATTACH=CONFIG]27767[/ATTACH],

3. full privileges are granted to u1 on the feature class ???A???

[ATTACH=CONFIG]27768[/ATTACH]

How come u1 is able to edit the default enterprise geodatabase "H" without the need to create his own version?

[ATTACH=CONFIG]27769[/ATTACH]

I thought that a user is created on the database to be able to create his own version and then to edit it but not to be able to edit the default database!


What might be the issue here?


Thank you

Best
Reply
0 Kudos
1 Solution

Accepted Solutions
Highlighted
New Contributor III
If pemission of Defult version is public and user is granted privileges in ArcCatalog, user can edit data on Default version.

-TT

View solution in original post

Reply
0 Kudos
6 Replies
Highlighted
New Contributor III
If pemission of Defult version is public and user is granted privileges in ArcCatalog, user can edit data on Default version.

-TT

View solution in original post

Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

If pemission of Defult version is public and user is granted privileges in ArcCatalog, user can edit data on Default version.

-TT


Many thanks Nguyen for the help,

Then all what I need to do is to switch the �??access�?� type of the sde.default from �??public�?� to �??protected�?�. In this case, the assigned users to this enterprise geodatabase will not be able to edit it. Also, they need to create their own versions from the sde.default and start editing it.


[ATTACH=CONFIG]27772[/ATTACH], [ATTACH=CONFIG]27773[/ATTACH], [ATTACH=CONFIG]27774[/ATTACH]


Best

Jamal
Reply
0 Kudos
Highlighted
New Contributor III
Hi!

- To change permission public to protect, do steps below:
Open ArcCatalog, connect to database (use sde or sa user account) --> click right on database --> choose version.
After that, select default version and click right on selected version --> choose properties: click option protect.
[ATTACH=CONFIG]27776[/ATTACH]
- Only sa or sde user can grant privileges for other user.
- User who create a version will own that version.
- Only sa, sde user or owner version can delete that version.

That's what I know, 🙂

--TT
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: mboeringa2010

And remember it is better to create database roles (e.g. "database viewer", "database editor", "Ramallah utilities editor" etc.), and to assign Feature Class privileges (SELECT, INSERT, UPDATE, DELETE) to the roles, instead of individual database users, like you are doing here in your screenshots.

Than assign the roles to individual database users. This will allow for far easier and more consistent privileges management.
Reply
0 Kudos
Highlighted
Honored Contributor
Hi!

- To change permission public to protect, do steps below:
Open ArcCatalog, connect to database (use sde or sa user account) --> click right on database --> choose version.
After that, select default version and click right on selected version --> choose properties: click option protect.
[ATTACH=CONFIG]27776[/ATTACH]
- Only sa or sde user can grant privileges for other user.
- User who create a version will own that version.
- Only sa, sde user or owner version can delete that version.

That's what I know, 🙂

--TT



Many thanks Nguyen. Very useful. It works fine

Best

Jamal
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: ThachThao

Many thanks Nguyen. Very useful. It works fine

Best

Jamal


:), you are welcom!
Reply
0 Kudos