Reputation
561
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 8
Newest
 Scholar
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 18 votes cast
Feb
27
answered What is an effective way to record rationales behind product design decisions?
Feb
27
comment What is an effective way to record rationales behind product design decisions?
I don't think the source code is an appropriate place to document design decisions. In any project you may have hundreds of source files. I don't want my design to be spread out all over the place. Source code comments are fine to indicate why something is done there in the code, but larger design decisions that @henrebotha is talking about should live in some kind of overarching document, IMO.
Jan
29
answered API design dilemma: to REST or not to REST
Sep
28
awarded  Scholar
Sep
28
accepted Identity propagation using Azure service bus
Sep
24
answered OAuth2 ROPC vs Basic Auth for public REST APIs?
Sep
24
awarded  Commentator
Sep
24
comment Identity propagation using Azure service bus
Thanks for your answer. Are you aware of implementations flowing security tokens in the message properties? I assume producers have to take precautions that the tokens are not about to expire when writing to the service bus. Any other considerations?
Sep
24
awarded  Student
Sep
24
asked Identity propagation using Azure service bus
Sep
23
comment CQRS without using others patterns
The link now points to a Chinese site selling footware. :(
Sep
14
awarded  Critic
Sep
12
comment OAuthv2 authorization grants
@smeeb, typically your access tokens also contain authorization info (what can the user do in the application or what roles he/she is in). This would differ per application, so you'd need different access tokens. You also might have users that have access to one application, but not the other.
Sep
12
answered OAuthv2 authorization grants
Aug
28
answered Best practice to authenticate third party to a website?
Jul
29
awarded  Yearling
Jul
29
awarded  Yearling
Jul
29
comment Auth options for distributed systems
Thanks and good luck! You can always post here or on SO if you run into issues.
Jul
29
awarded  Mortarboard
Jul
29
comment Auth options for distributed systems
No worries, you're welcome. Scopes are really a mechanism to determine what a 3rd party can do in your API. For example a finance application that can only read your account balance in your bank site. But since the JWT token contains the user's name and optionally even roles, you can look up in a database what a user or user in a role is allowed to do. That's also how my company is doing it.