Uploaded image for project: 'MidPoint'
  1. MidPoint
  2. MID-5883

Activation capability native Vs. configured

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 3.9
    • 3.9.1, 4.1, 4.0.2
    • None
    • Active subscription

    Description

      Again, the everlasting problem with resource capabilities configured Vs. native. When following capabilities are used, the account is always read as DISABLED on latest mp 3.9:

      <capabilities>		
      		<native xmlns:cap="http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3" xsi:type="c:CapabilityCollectionType">
      			<cap:schema />
      			<cap:testConnection />
      			<cap:create />
      			<cap:read />
      			<cap:update />
      			<cap:delete />
      			<cap:script>
      				<cap:host>
      					<cap:type>connector</cap:type>
      				</cap:host>
      			</cap:script>
      			<cap:addRemoveAttributeValues />
      			<cap:activation>
      				<cap:status />
      			</cap:activation>
      		</native>
      		<configured xmlns:cap="http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-3" xsi:type="c:CapabilityCollectionType">
      			<cap:addRemoveAttributeValues />
      			<cap:activation>
      				<cap:enabled>true</cap:enabled>
      				<cap:status>
      					<cap:enabled>true</cap:enabled>
      					<cap:returnedByDefault>true</cap:returnedByDefault>
      					<cap:ignoreAttribute>true</cap:ignoreAttribute>
      				</cap:status>
      				<cap:validFrom>
      					<cap:enabled>false</cap:enabled>
      				</cap:validFrom>
      				<cap:validTo>
      					<cap:enabled>false</cap:enabled>
      				</cap:validTo>
      				<cap:lockoutStatus>
      					<cap:enabled>false</cap:enabled>
      				</cap:lockoutStatus>
      			</cap:activation>
      			<cap:liveSync>
      				<cap:enabled>false</cap:enabled>
      			</cap:liveSync>
      			<cap:testConnection />
      			<cap:create />
      			<cap:read />
      			<cap:update />
      			<cap:delete>
      				<cap:enabled>false</cap:enabled>
      			</cap:delete>
      			<cap:script>
      				<cap:enabled>false</cap:enabled>
      			</cap:script>
      		</configured>
      	</capabilities>
      

      Only when whole <cap:activation> part is completely removed from configured and moved to native capabilities, all is allright. Tested on ScriptedSQL connector on multiple resources and on custom connector.

      Please fix Native Vs. Configured for good. Double check if there arent any problems with update delta=true even on master.

      Attachments

        Issue Links

          Activity

            People

              martin.lizner Martin Lizner
              martin.lizner Martin Lizner
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: