Closed nikosev closed 2 years ago
KUDOS to Nacho for spotting the misspelled word in content/en/users/aai/_index.md
I find those big tables used to provide specific info for each environement, very hard to read and review, both as markdown or in the rendered page where it can require scrolling.
Maybe when editing them it could be appropriate to move them to tabpanex
, see https://docs.egi.eu/about/contributing/shortcodes/#content-with-multiple-variants, as done at https://github.com/EGI-Federation/documentation/blob/5f05f9a4ed8e6d622c2e972005af8dda2caec246/content/en/users/aai/check-in/vos/_index.md?plain=1#L325-L358 and displayed on https://docs.egi.eu/users/aai/check-in/vos/#connection-parameters ?
Available at https://docs.egi.eu/documentation/457
@gwarf I would suggest to merge this PR and we will add the tabpanex
in the next PR in which we will add the Keycloak endpoints of the production OP.
@gwarf I would suggest to merge this PR and we will add the
tabpanex
in the next PR in which we will add the Keycloak endpoints of the production OP.
Deal! :)
Summary
Added Demo endpoints of the Keycloak based OP in the client migration guide