From: Krzysztof B. <kb...@un...> - 2020-03-10 19:25:52
|
Hi, W dniu 06.03.2020 o 13:31, D Baum pisze: > Hi, > > I'd like to define a saml (output) translation profile and understand > the handling of translation profiles better. > > Where is sys:saml defined? I can't find the translation profile > definition screen in the console, only the example json files in the > samples folder. But there's not json file for sys:saml that I could find. We have a ticket to bring also translation profiles view, for the shared ones (mostly sys:*). Besides watching it in AdminUI (as you discovered in other email) there is also one more trick you can use in console. In translation profile editor you have the "include" statement. Include a system profile you want to inspect. Then in the rule's menu (hamburger on top right) there is expand action. It will replace the include rule with all the statements of the included profile. > I assume json is now the preferred way of defining profiles? How can I > load them? Or, if defining profiles in the UI is still possible: where > is that located? No, JSON is not the preferred way. Defining profiles in UI was moved where it belongs: to the places where the profiles are used. That is input profiles are part of (remote) authenticator configuration, and output profiles can be defined and edited in IdP configurations. HTH, Krzysztof |