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

New feature: Configurable AccessToken and RefreshToken #252

Conversation

dirkmoors
Copy link

Because I want to be able to implement custom AccessToken and RefreshToken models, I've implemented a customizable AccessToken and RefreshToken, in the same way that the Application model was already configurable via the settings

@dirkmoors dirkmoors changed the title Implemented configurable AccessToken and RefreshToken [WIP] Implemented configurable AccessToken and RefreshToken May 22, 2015
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.78%) to 95.16% when pulling 6a8b1fa on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.3%) to 95.63% when pulling 77c9208 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.7%) to 95.24% when pulling 025db21 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 5764593 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 5764593 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 5764593 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@dirkmoors dirkmoors changed the title [WIP] Implemented configurable AccessToken and RefreshToken New feature: Configurable AccessToken and RefreshToken May 22, 2015
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 264d307 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 264d307 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 264d307 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.62% when pulling 264d307 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 78efc3a on evonove:master.

@masci
Copy link
Contributor

masci commented May 23, 2015

👍 Looks good to me

@masci masci added this to the 0.9.0 milestone May 23, 2015
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.68% when pulling e975ec9 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 0300402 on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.68% when pulling 87446b3 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 0300402 on evonove:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.31%) to 95.68% when pulling 87446b3 on dirkmoors:feature/custom-accesstoken-and-refreshtoken into 0300402 on evonove:master.

@pySilver
Copy link

pySilver commented Oct 8, 2015

any news on this?

@palazzem palazzem modified the milestones: 0.9.0, 0.10.0 Oct 15, 2015
@synasius synasius modified the milestones: 0.11, 0.10.0 Dec 14, 2015
@dfeinzeig
Copy link

Seems this could be used to implement JWT as the access tokens?

@clintonb
Copy link
Contributor

This would greatly help those of use who want to use JWT access tokens. See #368 and #343.
@dirkmoors @masci @palazzem @synasius what can we do to get this released?

@menecio
Copy link

menecio commented Apr 26, 2017

Already implemented on #467 and landed on master

@jleclanche I think this one can be closed also.

@jleclanche jleclanche closed this Apr 26, 2017
@duaneking
Copy link

Just to double check: Was anything a part of this what was not covered by #467 that would be good for #397 or JWT support in general?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet