feat: Add minimal client implementation for auth services

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.

[Giriharan219]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

This PR adds some client methods for auth endpoints and testing for these endpoints.

Why should this Pull Request be merged?

This Minimal client for auth APIs will enable users to more easily interact with that APIs.

What testing has been done?

Auto testing is included against NI's test tier.

API Link: Swagger-link

[santhoshramaraj]

Naming this AccessControlClient makes it intuitive and clubs the related feature across multiple services under the same client.
@mure, @spanglerco, @cameronwaterman - please share your thoughts

[ChrisStrykesAgain]

@santhoshramaraj I think that it's worth leaving this as-is (auth), then creating a secondary API specifically to expose access control functionality (creating/changing roles and/or workspace permissions management), as they are closely related, but really two different concepts.

As I mentioned in my comments, I think the auth functionality is pretty fundamental and might be worth somehow incorporating into the base class itself, but access control definitely doesn't belong there.

[ChrisStrykesAgain]

Most of this functionality seems pretty core to the fundamental operations. Would it make more sense to bake this into a base class shared across the various APIs instead of having an explicit API just for this?

[ChrisStrykesAgain]

@santhoshramaraj@spanglerco@cameronwaterman I need this functionality for a project I'm working on. If you're OK with the functionality being built into the base class (my preference per my last comment), I'll implement it here pretty quickly. If not, can we get this PR approved and/or any last comments/changes requested? Thanks!

[ChrisStrykesAgain]

Actually, thinking through this a little:

The thing I need, and what I think should really be in the base class is a "get workspace by name" method. The cleanest approach here would probably be to keep auth as it's own class (so basically what's in this PR) and add a class member variable of this type to the base class. I'd prefer to create a wrapper over the "get workspace" function to promote it to a first-class member, but then you'd still have the auth methods available to you as calls on the class member itself.

Does that seem reasonable?

[ChrisStrykesAgain]

I think this would use an instance of HttpConfiguration and not JupyterHttpConfiguration, right? Or am I missing something? I guess it depends on context. Might be worth a clarifying note, though, as users very well may be running in something other than a JupyterHub environment.