Cannot get js clients to work with OP server, keeps error-ing out

Hi @joeaudette ,

First of all, Thank you very much for building this amazing multi tenant solution! It answers many questions that have puzzled me for months.

I am getting an error whilst trying to test the JS clients on the cloudscribe-idserver-nodb sample.

OP server fires up fine, and I can login as admin and inspect the clients.

I fire up the Tenant1JsClient, and this also works fine. When I hit login I get directed back to OP server as expected by I get this error immediately.

Unexpected Error Well, this is embarrassing. An error occurred while processing your request. Rest assured, this problem has been logged and hamsters have been released to fix the problem.

the URL in the browser displays this: http://localhost:5000/home/error?errorId=2d859dcbd2599afc1ad10724b22748e852dd866cce6525c852282535b6fb98a4

I noticed with the sample OP server, the client url for client1 was actually http://localhost:5003. But Client1 was actually set to use port 5005, so I changed this in the OP admin to match, otherwise it was erroring out big time.

But at this stage, I cannot see why the JS client cannot authenticate. Is there any logging I can look at so I can determine what the issue is? and... Is this sample working for you also? or have some breaking changes happened which means this sample needs updating?

Kind Regards

Nigel Dewar

joeaudette / cloudscribe.StarterKits

Cannot get js clients to work with OP server, keeps error-ing out #7