Delete vs Replace when removing ExpirationTime with open source RM Client RRS feed

  • Question

  • I've been using the codeplex Resource Management Client, I noticed however inconsistent behavior with the ExpirationTime attribute.

    I am running FIM 2010 4.0.3594.2.

    According to the RmClient source code, attribute change operations consists of the following:

     public enum RmAttributeChangeOperation {
            /// <summary>
            /// None.
            /// </summary>
            None = 0,
            /// <summary>
            /// Add a value to a multi valued attribute.
            /// </summary>
            Add = 1,
            /// <summary>
            /// Remove a value from a multi valued attribute.
            /// </summary>
            Delete = 2,
            /// <summary>
            /// Replace the value of a single valued attribute.
            /// </summary>
            Replace = 3

    For removing single valued attributes you typically send a request with a "Replace" operation of null. This seems to be working fine for all attributes except for the ExpirationTime. The only way I can remove the ExpirationTime's value is to use a "Delete" request instead.

    I'm curious as to how the Portal handles removing the ExpirationTime versus this open source client. Is this a bug/feature in the RMClient or with the FIM Web Services? Has it been addressed in FIM 2010 R2 or newer hotfixes?

    Friday, December 21, 2012 5:39 PM