Skip to content
This repository has been archived by the owner on Jul 15, 2021. It is now read-only.

Auto-authorize developer access #40

Open
BK01 opened this issue Jan 5, 2018 · 4 comments
Open

Auto-authorize developer access #40

BK01 opened this issue Jan 5, 2018 · 4 comments
Assignees

Comments

@BK01
Copy link
Contributor

BK01 commented Jan 5, 2018

Provide API owners with a feature in GWA that allows them to select a group to contain developers (i.e. apiname_gh_group) and have any new developer that self-registers and becomes a member of the bcgov-keygen org automatically added to that group.

In short, IF enabled by the API owner through GWA, automatically provide registered developers with access to their API. Rather than, the current approach of having developers look-up your email in BCDC, then emailing you to request access.

@pauldaustin
Copy link

Add a github group which all github keygen users are in.

@BK01
Copy link
Contributor Author

BK01 commented Jan 25, 2018

accomplish via adding a g.. or i.. group. to investigate.

@pauldaustin
Copy link

Plan will be to add the gwa_github_developer ACL (group) for any user (consumer) in the BCGOV GitHub org the role. Then endpoints can be configured with the gwa_github_developer group permission and also use that for the developer key group. Api's can choose not to use that group and have their own manual group instead.

@pauldaustin pauldaustin self-assigned this May 22, 2018
@pauldaustin
Copy link

I'm going to improve the group name entry so that it does an autocomplete drop down when you start typing a group name.

@pauldaustin pauldaustin assigned BK01 and unassigned pauldaustin May 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants