XF 2.3 Oauth2 Client - Cannot get scope to show up on consent page

[stromb0li]

I have an add-on I'm building, but am struggling to identify why I cannot see the api scope I have defined showing up on the user conscent page:

<?xml version="1.0" encoding="utf-8"?>
<api_scopes>
  <api_scope api_scope_id="myapp:delete_hard"/>
  <api_scope api_scope_id="myapp:read"/>
  <api_scope api_scope_id="myapp:write"/>
</api_scopes>

In phrases.xml, I have three corresponding entries as well:

<?xml version="1.0" encoding="utf-8"?>
<phrases>
 <phrase title="api_scope.myapp_delete_hard" version_id="1000000" version_string="1.0.0"><![CDATA[Delete hard MyApp]]></phrase>
  <phrase title="api_scope.myapp_read" version_id="1000000" version_string="1.0.0"><![CDATA[Read MyApp]]></phrase>
  <phrase title="api_scope.myapp_write" version_id="1000000" version_string="1.0.0"><![CDATA[Write MyApp]]></phrase>
</phrases>

routes.xml

<?xml version="1.0" encoding="utf-8"?>
<routes>
  <route route_type="api" route_prefix="myapp" controller="stromb0li\MyApp:MyApp"/>
</routes>

I show the permissions on the OAuth2 client in Admin CP are checked, but still don't see them on the user consent page. If I uncheck another add-on or core api scope, I see them added/removed from the list accordingly; so I've overlooked something; just not sure what.

 

[Kirby]

I am not sure if I fully unserstand what you are asking here ...

As far as I understood you're building a XenForo Add-on that runs on the provider side and defines 3 API scopes (myapp:delete_hard, myapp:read & myapp:write).
On that XenForo instance you've configured an OAuth2 client and set those 3 scopes as allowed.

When a client that is using the created credentials rediects to the XenForo instance the scopes do not show up on the consent page.

Ist that correct?

If so:
Which software do you use on the consumer side?
What is the URL you see in the address bar of the consent page?

 

[stromb0li]

What is the URL you see in the address bar of the consent page?

That was it! Forgot to request for the parameter from the client

 

[Kirby]

That's kinda what I expected

 

[stromb0li]

Always helps