2.0 Q&A issues #1643
Description
This issue is to keep track of the findings we do during our 2.0 Q&A tests that need to be taken care of before releasing a new version.
- 1. Error pages are not translated properly
- 2.
Asset-files are generated from source to assets - 3. Legacy-routes do not work
- 4. Auto-generated entityID points to legacy metadata-endpoint; relates to point 3.
- 5. Move directories following https://github.com/php-pds/skeleton
- 6. Logs are cluttered with NameID generation warnings
1. Error pages are not translated properly
Details
We need to replace the old translation-tags in lib/SimpleSAML/Error/ErrorCodes.php as well.
2. Asset-files are generated directly from source
This is problematic for generating css-files with the same name as js-files and can be easily fixed by generating them in an intermittent build directory and then copy them from there to the www/assets-directory
Nobody seems to know how this webpack black magic works.. Not letting this block our new release
3. Legacy-routes do not work
Details
The legacy-routes for the scripts that resided in the `www/` directory do not work. We need to restore the php-files and manually redirect to the new controllers in the `saml` module.** Unless ** we can reach consensus in dropping the legacy routes & scripts completely and tell people how to configure their webserver to be able to use them
4 Auto-generated entityID points to legacy metadata-endpoint; relates to point 3.
Details
Proposed solution: stop auto-generating entityIDs and make the entityID setting mandatory5 Move src/ to resources/ and lib/ to src/
Details
Move src/ to resources/ and lib/ to src/6 Logs are cluttered with NameID generation warnings
Details
The following warning show up when only setting the saml:TransientNameID authproc: "Unable to generate NameID. Check the simplesaml.nameidattribute option."It shouldn't do that