Closed Nazarah closed 6 years ago
Verified in nightly.apinf.io with completely new email address used to register fiware account.
I have been able to debug this error.
It seems that meteor is expecting a username field to be provided, but this field is not being provided as part of the account data generated by apinf-fiware package.
So in AccountsServer.Ap._attemptLogin (packages/accounts-base/accounts_server.js) the field result.error contains something like "Missing Username field", which is then included in attempt.error which (not sure why) generates a circular JSON error.
Anyway, I have included the username field within the serviceData provided by the package and that seems to solve the problem.
This have been provided in apinf-fiware repo in PR 23, although I have not yet included the tests
https://github.com/apinf/apinf-fiware/pull/23 closes this.
reopening this issue as it has emerged in release 0.55.0 in https://staging.apinf.io This case registering attempt using fiware shows server error.
Also login isn't possible.
CC. @preriasusi
Works now fine on nightly and saas. Closing again
I am facing the same issue. The installation of APInf is done using docker-compose. I am using apinf/api-umbrella:0.15.0-apinf2 docker image for API-Umbrella and apinf/platform:0.58.0 docker image for APInf. I have created the separate issue for this Issue:3727
Steps to Reproduce:
(required: Fiware login to be active in the environment)
Outcome: User can't sign in using created fiware account. Page shows Internal Server Error
Expected Behavior: Users should be able to sign in to APInf platform with valid credentials used for Fiware account.
Environment: Windows 10, Chrome browser (latest), IE11, APInf Staging (https://staging.apinf.io) Fiware information in staging environment:
Cases verified