Hey Vincent,
I am quite certain that the problem arises from the fact that the developers are very actively working on the SAML implementation. You use SeaTable 3.3.7, but the configuration is for SeaTable 3.4.8. To be fair: this is not your fault, and the manual did not tell you that.
Here is the chnge request for this part of the manual from Febr. 17th:
By the way: with SeaTable 3.5 or 4.0 the SAML implementation will be much easier. Then only some parameters will be needed.
Back to your issue: I see two possible solutions. Tomorrow we will publish SeaTable 3.4.8 to docker hub and then the manual should match with your version. Or you change the configuration back to your 3.3.7 version. This would mean:
- Remove ATTRIBUTE_MAP_DIR
- Remove SAML_CONFIG: { attribute_map_dir
- Add SAML_METADATA_REMOTE_URL
- Add SAML_PROVIDER_DOMAIN
- Add SAML_ENTITY_ID
In either way: I will try to support you in implementing it.
Christoph
