Announcement Announcement Module
Collapse
No announcement yet.
Adding new scopes Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Adding new scopes

    Hi there,

    the sample oauth client spec includes scopes such as read, write. What if I want to have a scope named 'customer' - is this possible? I tried it once but I got errors at startup. Is there some extra implementation required here?

    Once we get the scope defined, I understand that I can use a role like SCOPE_CUSTOMER for example in the <http> tag for limiting the access, right? I guess I can use the same with the annotations on individual controller methods then.

  • #2
    Originally posted by hansamann View Post
    the sample oauth client spec includes scopes such as read, write. What if I want to have a scope named 'customer' - is this possible?
    Scopes are just strings, so you can use any value you like - it's a contract between the client and the Resource Server. If there are any scopes registered with a client then no token will be issued with any other value, but that's the only restriction placed by the Authorization Server.

    Once we get the scope defined, I understand that I can use a role like SCOPE_CUSTOMER for example in the <http> tag for limiting the access, right? I guess I can use the same with the annotations on individual controller methods then.
    Yes that should work.

    Comment

    Working...
    X