On 04/07/2015 10:51 AM, Prashant Bapat wrote:
Hi Thierry,

Thanks for the reply.

Turned out that the slapi-plugin was not ignoring the replicated operations. Problem solved.

Great news !

regards
thierry

Regards.
--Prashant

On 6 April 2015 at 23:25, thierry bordaz <tbor...@redhat.com <mailto:tbor...@redhat.com>> wrote:

    Hello Prashant,

        If you are able to reproduce the problem (ipasshpubkey not
        replicated), would you enable replication and plugin logging
        
(http://directory.fedoraproject.org/docs/389ds/FAQ/faq.html#Troubleshooting)
        and provide the access/errors logs ?

        thanks
        thierry

    On 04/06/2015 04:38 PM, Prashant Bapat wrote:
    Hi,

    Seems like there is an issue with replication that I have
    encountered.

    I'm using a custom attribute and a slapi-plugin. Below is the
    attribute added.


    dn: cn=schema
    changetype: modify
    add: attributeTypes
    attributeTypes: (2.16.840.1.113730.3.8.11.31.1 NAME
    'ipaSshSigTimestamp' DESC 'SSH public key signature and
    timestamp' EQUALITY octetStringMatch SYNTAX
    1.3.6.1.4.1.1466.115.121.1.40 X-ORIGIN 'APIGEE FREEIPA EXTENSION' )
    -
    add: objectclasses
    objectclasses: ( 2.16.840.1.113730.3.8.11.31.2 NAME
    'ApigeeUserAttr' SUP top AUXILIARY DESC 'APIGEE FREEIPA
    EXTENSION' MAY ipaSshSigTimestamp )

    This is the only change.

    Problem: I'm using a python script calling the user_add and
    user_mod to add user and then add ssh key to the user. After this
    the custom attr (ipaSshSigTimestamp) is getting replicated to the
    other master but the standard ipaSshPubKey is not.

    This had happened once before in the exact same setup. I removed
    the second master and re-installed it and it was working. But
    same problem again.

    Any pointers appreciated.

    Regards.
    --Prashant





-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to