Fiware pep-proxy and idm communication issue about fiware-pep-proxy HOT 5 OPEN

Hey i was working on same thing as u are now, differences between config files u are seeing are versions. Docker one is 5.4 version of pep-proxy, while version u downloaded from github is latest version that is why there are many differences between them.

About error with Unauthorized issue, in version 5.4. Solution

From my short experience of tying to setup them, i think that best way is using latest versions of both but currently there is bug with pep-proxy when u put invalid/wrong token. Older versions depend on keystone/horizon with could lead to more bugs.

from fiware-pep-proxy.

Firstly , thanks for your reply . I've deployed both of the latest versions of pep-proxy and idm from these links . https://github.com/ging/fiware-pep-proxy , https://github.com/ging/fiware-idm .
I've also configured the pep-proxy as follows

// Set this var to undefined if you don't want the server to listen on HTTPS
config.https = {
    enabled: false,
    cert_file: 'cert/cert.crt',
    key_file: 'cert/key.key',
    port: 443
};

config.idm = {
        host: 'localhost',
        port: 3000,
        ssl: false
}

config.app = {
        host: 'www.google.com',
        port: '80',
        ssl: false // Use true if the app server listens in https
}


// Credentials obtained when registering PEP Proxy in app_id in Account Portal
config.pep = {
        app_id: 'XXXXXXXXX',
        username: 'XXXXXXXX',
        password: 'XXXXXXXX,
        trusted_apps : []
}

// in seconds
config.cache_time = 300;

and on starting the idm and pep-proxy , i get a token as shown in the following log

and this is the log of the idm

and when i test the pep-proxy with the idm by sending a request with the provided token i get an empty reply from server as follows

these are also the logs of the pep-proxy after sending the request .

now i hope my case is much clearer and that there's a solution
@IgorDespot

from fiware-pep-proxy.

I post current state in edited for issue hope is much clearer and that there's a solution @IgorDespot

from fiware-pep-proxy.

There is solution for everything , but if u cannot wait for this issue to be fixed then use older version of idm and pep-proxy(5.4). That is what i have done. Your update link is not valid u have extra stuff "to, that link works with older versions of pep and Willma if u used that guide in combo with latest version it wont work. @AhmedEmad031

from fiware-pep-proxy.

Could you please specify Which version of idm should I use to communicate with pep proxsy and Authorization PDP as I need to build advanced security senario ? @IgorDespot

from fiware-pep-proxy.