Skip to content

Add issuer to auth#19

Merged
kw217 merged 3 commits intomasterfrom
add-issuer-to-auth
Sep 22, 2017
Merged

Add issuer to auth#19
kw217 merged 3 commits intomasterfrom
add-issuer-to-auth

Conversation

@kw217
Copy link
Copy Markdown
Contributor

@kw217 kw217 commented Sep 22, 2017

After discussion re #14 we agreed to add issuer - knowing who did something is very important for audit purposes; just knowing who it was done to is not enough. Also it is useful to be able to report per-issuer (i.e., per-third-party-app) statistics from server applications, and this is easier if that information is present within the application (rather than just in logs).

We agreed to drop auth_type and expiry_deadline. The first (auth_type) would encourage services to have auth-type-dependent behaviour, making the testing matrix more complex; the second (expiry_deadline) is not actually useful - authenticators may wish to do internal caching based on deadlines, but the validity period of the auth data doesn't imply anything about the validity period of the requester's authorization.

This is a breaking change (new field in struct), hence there is a version bump. If approved, I'll tag and release the library to cargo.

@kw217 kw217 requested a review from mirw September 22, 2017 09:28
Comment thread CHANGELOG.md Outdated
- Start of changelog.

[Unreleased]: https://github.com/olivierlacan/keep-a-changelog/compare/0.5.0...HEAD
[0.5.0]: https://github.com/olivierlacan/keep-a-changelog/compare/0.4.0...0.5.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

D'oh, thanks.

Comment thread src/auth.rs Outdated
pub scopes: Scopes,
/// Authenticated identity of the party to which
/// authorization has been granted, if available
/// (i.e., who is doing the accessing).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is "who is doing the accessing" actually correct here (or, at least, is it over simplifying)? If I make a request to microservice X to access microservice Y to retrieve data from store Z, you could say that X, Y and Z are all doing the accessing, but I think the issuer would still be me. Correct? Maybe it's better to either drop the simplified explanation, or flesh it out?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've fleshed it out a bit, with reference to RFC6749 and RFC7519. Hopefully this is better?

@kw217 kw217 assigned mirw and unassigned kw217 Sep 22, 2017
@mirw
Copy link
Copy Markdown
Contributor

mirw commented Sep 22, 2017

Looks good.

@mirw mirw assigned kw217 and unassigned mirw Sep 22, 2017
@kw217 kw217 merged commit 342617b into master Sep 22, 2017
@kw217 kw217 deleted the add-issuer-to-auth branch September 22, 2017 16:31
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.

2 participants