Test retrieving an authorization code using a confidential client with a
bad redirect URI
The redirect URI is registered with this client, so passing a redirect that
doesn't match the registered value should generate an error per the OAuth
2.0 spec.
Test retrieving an authorization code using a confidential client
Client authentication is not required for confidential clients accessing
the authorization endpoint
Test retrieving an authorization code using a confidential client without
setting redirect URI
The redirect URI is registered with this client, so omitting it should
still generate a response using the registered redirect URI.
Expected response for app data in json:
{
"entry" : {
"jane.doe" : {"count" : "7"},
"george.doe" : {"count" : "2"},
"maija.m" : {}, // TODO: Should this entry really be included if she doesn't have any data?
}
}
Expected response for app data in json:
{
"entry" : {
"jane.doe" : {"count" : "7"},
"george.doe" : {"count" : "2"},
"maija.m" : {}, // TODO: Should this entry really be included if she
doesn't have any data? } }
s