oAuth 2

In comparison to our previous, fully API-based implementation, current auth-service version fully supports OAuth2 PKCE-based authorization flow and thus contains UI (Frontend) part to interact with users and backend API to interact with applications (Web or Mobile). The only supported way to authenticate users is an interactive login: this is why auth-service now contains UI part.

Not that at first new login attempt each user should empty cache.

Example mHealthINX

Please check the video for the mHealthINX project. In order to access the API's please use https://mhealthinx-backend.medvision360.org/v2/api-docs. Check at the bottom of this page if you need help.

We fix languages and Swagger API asap.