[ 
https://issues.apache.org/jira/browse/DERBY-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269621#comment-13269621
 ] 

Rick Hillegas commented on DERBY-5747:
--------------------------------------

I think we should stay focused on the issue of credentials management and not 
veer off into the management of authorization ids. The term "user" covers both 
topics. A couple random thoughts:

1) Right now, the DBO can disable an account by dropping its credentials. The 
DBO may need to disable an account until a security threat is cleared. You 
don't want the account's data to disappear in this situation.

2) Cascaded drop of an authorization id is a fair-sized project. It implies 
cascaded DROP SCHEMA. That, in turn, implies implementing cascade semantics for 
all statements which DROP objects.

Thanks,
-Rick
                
> Native user authentication: Docs do not describe what happens to schema and 
> its SQL objects on SYSCS_UTIL.SYSCS_DROP_USER call
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5747
>                 URL: https://issues.apache.org/jira/browse/DERBY-5747
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation, Services
>    Affects Versions: 10.9.0.0
>            Reporter: Dag H. Wanvik
>         Attachments: repro2.sh
>
>
> Currently, the schema and the objects remain after the user is dropped, cf. 
> repro2.sh attached.
> The authorization id of the schema of the dropped user is still that id 
> (dangling) after DROP.
> Perhaps ownership should revert to the DBO when a user is dropped, or should 
> DROP USER do a cascade delete?
> There is no way currently to change the ownership of the schema to another 
> user.
> At the very least we should document what happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to