Unable to access Omnicept developer's console, recover access keys or use existing keys.
We are developing a number of Unity apps that use the Omnicept SDK Unity plugin. Recently when trying to login to the Omnicept console we are met with error 5709 saying that "We regret that due to U.S. legal restrictions, we are unable to process your transaction". This means we cannot review our existing apps on the console and recover our access keys.
Additionally when trying to create a new app via the HP Developer's portal we are unable to because the web form appears to be broken on all browsers. The required 'category' dropdown does not populate so a new app can't be created.
Finally, our Unity apps that already have the client ID and access keys added to the Omnicept configuration can no longer connect to the service. We get an error message saying "Connection rejected: LicensingPostHandshakeAction Error: License checkout failed with error: Forbidden. User is not allowed to make this request.: Login failure: The provided authorization grant or refresh token is invalid, expired, revoked, please login in again. Post handshake action execution failed". To be clear, these are apps that were running without issue a few days ago.
What is going on here? We are now completely locked out of any further development while we can't access the Omnicept service and it is very urgent for us to resolve this. We've had no response from our emails to support. I also see multiple other forum posts regarding this with no proper response from HP.
-
Switching the Unity config to Core mode allows us to now connect and access most of the sensors from the Omnicept service.
I'm still curious about what the situation is with Developer mode though in case we need to use cognitive load and heart rate variability. The online documentation still talks about the process of logging into the developer console and creating apps with access keys etc. - is this still the correct method?0 -
NGR Are you able to access Dev Console now and your existing keys?
0
Please sign in to leave a comment.
Comments
2 comments