Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Access resources requiring authentication #9

Closed
samperd opened this issue Mar 2, 2015 · 6 comments

Comments

@samperd
Copy link

commented Mar 2, 2015

Is there a way to access resources requiring authentication?

@hannesaddec

This comment has been minimized.

Copy link
Collaborator

commented Apr 12, 2016

What kind of authentication are you referring to ? HTTP, Cookies, SSL, Shibboleth OpenID, CAS?

@justb4

This comment has been minimized.

Copy link
Member

commented May 3, 2017

At least HTTP Basic Auth is used a lot, that would be a start. I take it that you need the ability to add credentials for a Resource URL? You could try to encode it in the URL like http://username:password@example.com/, not sure this will work in GHC, but also exposes creds via UI.

So, good point: could start adding optional user/password fields for a Resource.

@justb4 justb4 added the enhancement label May 3, 2017

@justb4 justb4 changed the title HTTP Error 401: Authorization Required Access resources requiring authentication Jun 29, 2017

mkofahl added a commit to faegi/GeoHealthCheck that referenced this issue Jan 24, 2018

mkofahl added a commit to faegi/GeoHealthCheck that referenced this issue Mar 7, 2018

@justb4

This comment has been minimized.

Copy link
Member

commented Jun 18, 2019

Finally this feature will be implemented! Planned:

  • generic/extensible Resource Auth design
  • implementation for HTTP Basic Auth

Current thinking:

  • new column/field for Resource auth
  • auth field stores encrypted JSON structure
  • auth JSON structure identifies Auth Method and Data properties
  • Auth Method id drives implementation

Something like:

{
method: 'basicauth',
data: {
   username: 'rscuser',
   password: 'rscpasswd'
 }
}

The method id basicauth will direct the implementation to a BasicAuth class to use which fills in the proper headers etc.

@justb4 justb4 added this to the Version 0.7.0 milestone Jun 18, 2019

@justb4 justb4 moved this from To do to In progress in Stantec NL sponsored development Jun 18, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jun 24, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jun 30, 2019

@justb4 justb4 self-assigned this Jun 30, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jul 2, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jul 2, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jul 3, 2019

justb4 added a commit to justb4/GeoHealthCheck that referenced this issue Jul 3, 2019

justb4 added a commit that referenced this issue Jul 3, 2019

Issue #9 resource auth (#259)
* #9 DB and generic structure for Resource.auth

* #9 first stab an generic Resource Auth via Plugins

* #9 finalized generic Resource Auth via Plugins

* #9 finalized generic Resource Auth via Plugins

* #9 finalized generic Resource Auth via Plugins - fix test

* #9 finalized generic Resource Auth via Plugins - msgs and translations
@justb4

This comment has been minimized.

Copy link
Member

commented Jul 3, 2019

Fixed via #259 , available on https://demo.geohealthcheck.org/

@samperd

This comment has been minimized.

Copy link
Author

commented Jul 8, 2019

@justb4, thanks so much for considering this feature in the latest stantec sponsored development activity.

@justb4

This comment has been minimized.

Copy link
Member

commented Jul 8, 2019

@samperd yes, you opened this a very long time ago! Does the current implementation work for you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.