Repository navigation
Add guidance for creating special purpose database users - #10503
Steve Jones (way0utwest) wants to merge 1 commit into
Conversation
Added section on creating special purpose users mapped to certificates or asymmetric keys.
|
Steve Jones (@way0utwest) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit c838e8b: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
🟡 Changes recommended
An active documentation issue remains because the description omits that both user types cannot log in or authenticate, which could mislead readers about their purpose.
1 open issue
What changed in this PR
Adds guidance for creating special-purpose database users mapped to certificates or asymmetric keys, complementing the existing database-user creation instructions.
Changes:
- Adds a "Create a special purpose user" subsection.
- Describes certificate-mapped and asymmetric-key-mapped users.
- Links to the
CREATE USERreference for additional details.
| File | Description |
|---|---|
| docs/relational-databases/security/authentication-access/create-a-database-user.md | Adds guidance for creating special-purpose database users mapped to certificates or asymmetric keys. |
Review effort: Lite
|
|
||
| #### Create a special purpose user | ||
|
|
||
| There are two special purpose users: a user mapped to a certificate and a user mapped to an asymmetric key. These users can be granted permissions and can sign modules. For more information, see [CREATE USER](../../../t-sql/statements/create-user-transact-sql.md). |

I can't edit the image, but I added a section on creating special purpose users mapped to certificates or asymmetric keys. The image says "special purpose logins", but these are special purpose users.