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.

Sign up for GitHub

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

Jump to bottom

HTTPS and Identity #77

Open
PanacheSoftwareDev opened this issue Aug 4, 2020 · 2 comments
Open

HTTPS and Identity #77

PanacheSoftwareDev opened this issue Aug 4, 2020 · 2 comments
Assignees
@PanacheSoftwareDev
Labels
enhancement New feature or request

Comments

@PanacheSoftwareDev
Copy link
Member

Although HTTPS can be used locally whilst debugging the platform, full https support is not yet included within the published docker images due to the requirements for certificates to be setup.

In addition to missing HTTPS in docker images, the identity service currently stores authorisation tokens within an in memory store. This needs to be adjusted to include IdentityServer stores within the database alongside the other authorisation data.
@PanacheSoftwareDev PanacheSoftwareDev added the enhancement New feature or request label Aug 4, 2020
@PanacheSoftwareDev PanacheSoftwareDev self-assigned this Aug 4, 2020
@PanacheSoftwareDev
Copy link
Member Author

At the moment the Swagger UI code for documenting WebAPI calls uses JWT Bearer authorization. It will be cleaner to move this to use OAuth against the Identity service to provide a login instead of needing the user to manually enter a token.

@PanacheSoftwareDev
Copy link
Member Author

PanacheSoftwareDev commented Aug 14, 2020 •
edited

Linked to Branch Identity/77-StorageChanges

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PanacheSoftwareDev PanacheSoftwareDev

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PanacheSoftwareDev