Skip to content
Snippets Groups Projects
Commit d0ce47dc authored by Taylor A Murphy, PhD's avatar Taylor A Murphy, PhD
Browse files

Merge branch 'tayloramurphy-master-patch-41456' into 'master'

Update snowflake user provisioning

See merge request gitlab-com/www-gitlab-com!23204
parents 7ddd6e8d 08e916be
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -436,15 +436,21 @@ This is the list of groups and their read/write permissions.
Here are the proper steps for provisioning a new user and user role:
 
* Login and switch to `securityadmin` role
* Create user (`EBURKE`)
* Create user
* User name: `JSMITH` - This is the GitLab default of first letter of first name and full last name.
* Create a password using https://passwordsgenerator.net/
* Click next and fill in additional info. Make Login Name and Display name match user name (all caps).
* Click next and fill in additional info.
* Make Login Name their email. This should match the user name just with @gitlab.com appended.
* Display name should match match user name (all caps).
* First and Last name can be normal.
* Do not set any defaults
* Send to person using https://onetimesecret.com/
* Create role for user (`EBURKE` for example) with `sysadmin` as the parent role (this grants the role to sysadmin)
* Create role for user (`JSMITH`) with `sysadmin` as the parent role (this grants the role to sysadmin)
* Grant user role to new user
* Grant any additional roles to user
* Add [future grant](https://docs.snowflake.net/manuals/sql-reference/sql/grant-privilege.html) to `analytics` and `analytics_staging` schemas to user with `grant select on future tables in schema <schema> to role <username>` using the `sysadmin` role
* Document in Snowflake config.yml permissions file
* User should also be able to login via Okta.
</div>
</div>
 
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment