search

ging / fiware-idm

OAuth 2.0-based authentication of users and devices, user profile management, Single Sign-On (SSO) and Identity Federation across multiple administration domains.
https://keyrock-fiware.github.io
MIT License
36 stars 81 forks source link

Invalid scope: Requested scope is invalid #66

Open ibstelix opened 5 years ago

ibstelix commented 5 years ago

Hello dear support, please help 2 weeks i am struggling to get work Biz Ecosystem with my local fiware-idm. It's working perfectly with the online lab but with my local fiware-idm it's trowing:

invalid_scope: Invalid scope: Requested scope is invalid at new InvalidScopeError (/opt/fiware-idm/node_modules/oauth2-server/lib/errors/invalid-scope-error.js:25:14) at /opt/fiware-idm/node_modules/oauth2-server/lib/grant-types/abstract-grant-type.js:117:17 at tryCatcher (/opt/fiware-idm/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/opt/fiware-idm/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/opt/fiware-idm/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromiseCtx (/opt/fiware-idm/node_modules/bluebird/js/release/promise.js:606:10) at Async._drainQueue (/opt/fiware-idm/node_modules/bluebird/js/release/async.js:138:12) at Async._drainQueues (/opt/fiware-idm/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues (/opt/fiware-idm/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) statusCode: 400, status: 400, code: 400, message: 'Invalid scope: Requested scope is invalid', name: 'invalid_scope'

ibstelix commented 5 years ago

It worked when i sent "permanent" as scope

johnnychoque commented 2 years ago

Hi @ibstelix, I get the same error with Biz Ecosystem. I understand that you have set the token type to permanent. I tried your suggestion but it did not work in my case. what version of Fiware-IDM do you use? I have tried it on versions 7.9.2 and 8.1.0 and both get the same error.

pierre-josselin commented 1 year ago

Got the same issue.

Setting BAE_LP_OIDC_ENABLED to false on the logic proxy solved the problem.

I guess turn on OIDC on the Keyrock app could fix that as well.