My reply to the user nitesh@fr.ibm.com :

Dear Nitesh,
I have just forwarded your request to the second level support for Orion Context Broker. They will contact you soon.

Best regards
Marco

Reply from the user:

Hi Marco,
Thank you for the response, but is there any way I can contact the support person. As I am unable to even generate a new Access Token (using wget --no-check-certificate https://raw.githubusercontent.com/fgalan/oauth2-example-orion-client/master/token_script.sh).

Nitesh

My reply to the user:

Dear Nitesh,
I’m sorry but I cannot put directly in touch with the support people.
About your issue, unfortunately, the installation of the new IDM has not been completed yet due to some problems. Our colleagues are working to solve the issues.
So I would suggest to try again tomorrow. Anyway you keep in mind that your request was already taken in charge from the second level support for Orion Context Broker. They will contact you soon.

Best regards
Marco

I'm trying to figure out if something regarding X-Auth-Token and the way of obtaining it have changed due to the migration. I have just sent IDM team an email about the issue.

User has been answered. Closing.

--------------------------------------

Dear Nitesh,

Regarding you query to FIWARE Lab support:

_Hi,
I am working on a project for Orange and make API calls to the Orion Context Broker as per (
https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_Quick_Start_for_Programmers ).

Today the API calls are failing (which i can understand) but once the maintenance is complete - will my old AuthToken still work? And how will I know that the idm changes are over?

Many thanks,

Nitesh_

Please, have a look to http://stackoverflow.com/questions/30193763/fiware-token-script-error-parsing-json-response/30232326#30232326, which I understand is the same problem. You will need to regenerate the token.

Thanks!

Beset regards,

------
Fermín