Roundtripping of adjudicator not possible

[kenneth-olwing]

This was seen during investigation for issue #968.

(...and TL;DR, I eventually started to look for the problem below in the code, and yes, I found that it apparently is a known issue :-). Can I assume this is still a 'bug to eventually fix' in a bug database? Any guess to a timeframe to hope for a fix? Any suggested workarounds?)

===

As it happens, doing a createDomain exposed a slightly different problem. As it happens, the original config.xml has this in the realm configuration:

      <sec:adjudicator xsi:type="wls:default-adjudicatorType">
        <wls:require-unanimous-permit>false</wls:require-unanimous-permit>
      </sec:adjudicator>

This, quite correctly, gives this in the yaml:

                Adjudicator:
                    Provider:
                        DefaultAdjudicator:
                            RequireUnanimousPermit: false

Unfortunately, a createDomain with this gives a warning:

####<2021-aug-20 20:54:03> <VARNING> <SecurityProviderCreator> <_check_provider_type> <WLSDPLY-12137> <Update of security configuration adjudicators is not supported>

Since it's seen during discoverDomain, one could reasonably expect it to roundtrip in createDomain.

[CarolynRountree]

there is a bug open, right now it is in WDT. We can move it up in the queue

[kenneth-olwing]

👍 , I'm good with that.

[CarolynRountree]

leave open for bug work