The cookies set by keycloak were not formatted correctly so the browser was
not taking them into account. Providing those additionnal directives fixes the
issue.
Before:
Set-Cookie: KEYCLOAK_SESSION=<T>; Version=1; Path=/;
SameSite=Laxrealms/drive/; Max-Age=36000; Secure; SameSite=None
After:
Set-Cookie: KEYCLOAK_SESSION=<T>; Version=1; Path=/realms/drive/;
SameSite=Lax; Max-Age=36000; Secure; SameSite=None
We want to add documentation showing how to use DS_Proxy with Drive.
With proxy is fully optionnal and is here if you want to an encryption
layer between Drive and the object storage.
In order to be able to test resource server we need to be able
to share a network between our docker compose stack. Let's add
a network to make it work.
We want to distinguish the url and the url_preview. The url_preview
property will be provided only if the mimetype is listed in the
ITEM_PREVIEWABLE_MIME_TYPES settings. Also an other route is added to
nginx forcing the content-disposition with the value attachment for
download url.
Set `sslRequired` to `none` for all realms in the keycloak dev service.
By default this settings is set to `external` and only local IPs are granted
to access to the server without SSL. But sometimes, with docker (desktop?)
it appears the network configuration may keycloak to consider the accessing
ip as not local.
We also took opportunity of this change to use the latest keycloak image version
Resolve#291
This commit, with contributions from Sylvain Grizard, adds support
for PaaS deployment platforms such as Scalingo, which build the
project on commit. It uses the La Suite Buildpack, which compiles
the frontend first as static files, and serves them along with
the backend with nginx.
