A native (desktop or mobile) application.
- API: This application can make API requests to FotoWeb. An API license is required.
- CONSENT: The authenticity of the application cannot be verified, so it has to ask for user consent upon every authorization.
- Refresh tokens can be used to keep the application permanently authorized.
In this example, the "native" application is simulated by a web application.
A legacy web application which uses FotoWeb embeddable widgets only and was written for an older version of FotoWeb.
- No application registration is necessary.
- CONSENT: The authenticity of the application cannot be verified, yet users are not asked for consent.
- SESSIONS: Users must authorize the application every time (no refresh tokens).
This approach may seem easier, but is deprecated and considered insecure. It exists in this example application only for testing purposes.
The option "Enable Legacy Selection Widget" must be enabled in the FotoWeb site settings.
This type of application is not supported in FotoWare SAAS.
The application must first be registered in your FotoWeb tenant.
For information on how to do this, please see
Application Registration.
and use the following application settings:
When done, please enter the generated application details (e.g., client ID) into the fields below.
You have selected the FotoWare demo server.
This application is already registered, and application details (client ID and client secret) need not be entered manually.
Your tenant URL uses HTTP, and this application is hosted on a HTTPS URL. Embedding FotoWeb widgets may be blocked by your browser due to Content Security Policy (CSP).
To work around this, you must either host this application on HTTP as well or host FotoWeb on HTTP.