[mitreid-connect] testing with MITRED package

[Justin Richer]

Note that those are the scopes available for the *system* and not the ones for a user logged in using OIDC. Those scopes are available as part of the token endpoint’s response in the “scope” field or available (from a protected resource) by introspecting the token.

The real question is: what are you trying to solve that you need these scopes? Which component needs to know?

 — Justin

> On Dec 15, 2016, at 3:28 PM, Steven Carmody <steven_carmody at brown.edu> wrote:
> 
> Yes, that works fine. Thanks very much !
> 
> On 12/15/16 3:10 PM, William Hadden1 wrote:
>> Is this what you are after?
>> 
>> http://<yourhost>/api/scopes <http://localhost:9090/api/scopes>
>> 
>> 
>>    ----- Original message -----
>>    From: Steven Carmody <steven_carmody at brown.edu>
>>    Sent by: mitreid-connect-bounces at mit.edu
>>    To: mitreid-connect at mit.edu
>>    Cc:
>>    Subject: [mitreid-connect] testing with MITRED package
>>    Date: Thu, Dec 15, 2016 6:33 PM
>> 
>>    Hi,
>> 
>>    I'm just starting, and I've installed the MITRED package as an embedded
>>    Jetty instance inside of Maven.
>> 
>>    My test program has made it through most of the protocol steps -- I'm
>>    able to obtain both an authorization grant and an access token. What is
>>    the endpoint I'd use in order to retrieve the scope values for the user
>>    that I logged in as ?
>> 
>>    thanks !
>>    _______________________________________________
>>    mitreid-connect mailing list
>>    mitreid-connect at mit.edu
>>    http://mailman.mit.edu/mailman/listinfo/mitreid-connect
>> 
>> 
>> 
>> Unless stated otherwise above:
>> IBM United Kingdom Limited - Registered in England and Wales with number
>> 741598.
>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>> 
> 
> _______________________________________________
> mitreid-connect mailing list
> mitreid-connect at mit.edu
> http://mailman.mit.edu/mailman/listinfo/mitreid-connect