Skip to content
This repository was archived by the owner on Dec 20, 2018. It is now read-only.

Integrated Web API client #1206

Closed
danroth27 opened this issue May 17, 2017 · 1 comment
Closed

Integrated Web API client #1206

danroth27 opened this issue May 17, 2017 · 1 comment
Assignees
@javiercn
Labels
enhancement identity-service
Milestone
Backlog

Comments

@danroth27
Copy link
Member

danroth27 commented May 17, 2017 •
edited by DamianEdwards
Loading

In order for you to use JWT bearer tokens with Identity, you need to configure the JWT bearer settings to know which singing key to use to validate the tokens. We optimize this today to avoid an HTTP client call for this but it is in the actual Web API project template. This work would factor that into the framework so that the template just needs to call that code.
@danroth27 danroth27 added this to the 2.0.0-preview2 milestone May 17, 2017
@DamianEdwards DamianEdwards mentioned this issue May 17, 2017
Open
7 tasks
@danroth27
Copy link
Member Author

@Eilon @javiercn I think we need this. Otherwise you have to a do a bunch of work to setup the JwtBearer options in an environment independent way.

@DamianEdwards DamianEdwards modified the milestones: 2.0.0, 2.0.0-preview2 Jun 1, 2017
@danroth27 danroth27 modified the milestones: 2.0.0, 2.1 Jun 5, 2017
@Eilon Eilon modified the milestones: 2.1.0, Backlog Apr 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@javiercn javiercn

Labels
enhancement identity-service
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@Eilon @DamianEdwards @danroth27 @javiercn