On Wed, 2013-02-13 at 09:35 -0500, Dmitri Pal wrote:
> On 02/13/2013 12:47 AM, It Meme wrote:
> > Could there be anyway that accounts can be provisioned to IPA, via
> > LDAP, from existing IAM system?
> >
> >
> > The newly provisioned accounts can be temporarily stored in IPA's
> > 389 Director
It Meme wrote:
Thank you for your reply.
Could there be anyway that accounts can be provisioned to IPA, via LDAP,
from existing IAM system?
The newly provisioned accounts can be temporarily stored in IPA's 389
Directory Server, and subsequently an automated task can IPA-ize the
accounts (i.e. v
On 02/13/2013 12:47 AM, It Meme wrote:
> Thank you for your reply.
>
> Could there be anyway that accounts can be provisioned to IPA, via
> LDAP, from existing IAM system?
>
> The newly provisioned accounts can be temporarily stored in IPA's 389
> Directory Server, and subsequently an automated tas
Thank you for your reply.
Could there be anyway that accounts can be provisioned to IPA, via LDAP,
from existing IAM system?
The newly provisioned accounts can be temporarily stored in IPA's 389
Directory Server, and subsequently an automated task can IPA-ize the
accounts (i.e. via the Python lib
On 02/12/2013 12:42 PM, It Meme wrote:
> Yes - Dmitri is correct.
>
> Our purchased IAM product has LDAP connectors. It is possible to customize to
> develop other connector protocols but it requires tweaking the core product
> code - this adds risk and, if not careful, could break our support w
Yes - Dmitri is correct.
Our purchased IAM product has LDAP connectors. It is possible to customize to
develop other connector protocols but it requires tweaking the core product
code - this adds risk and, if not careful, could break our support with vendor
or increase operational risk to a cr
On 02/09/2013 11:53 AM, John Dennis wrote:
> On 02/08/2013 05:29 PM, It Meme wrote:
>> Hi:
>>
>> Scenario:
>>
>> 1) User is created via LDAP call to IPA (i.e.the 389 Directory Server)
>>
>> The above user will not have IPA-specific attributes.
>>
>> Can we use the Python Library, or CLI, to modify
On 02/08/2013 05:29 PM, It Meme wrote:
Hi:
Scenario:
1) User is created via LDAP call to IPA (i.e.the 389 Directory Server)
The above user will not have IPA-specific attributes.
Can we use the Python Library, or CLI, to modify the account to IPA-ize it?
You're really better off using the IP
On 02/08/2013 06:33 PM, It Meme wrote:
> Hi Dmitri:
>
> Yes, we are evaluating ways of provisioning users and their group
> memberships for Joiner, Mover, Leaver (JML) events.
>
> We were thinking of your suggestion as an option and your reply was
> very helpful.
>
> Our expected real-time scenario
Hi Dmitri:
Yes, we are evaluating ways of provisioning users and their group
memberships for Joiner, Mover, Leaver (JML) events.
We were thinking of your suggestion as an option and your reply was very
helpful.
Our expected real-time scenarios is probably 5 mins latency.
Is it viable to explore
On 02/08/2013 05:29 PM, It Meme wrote:
> Hi:
>
> Scenario:
>
> 1) User is created via LDAP call to IPA (i.e.the 389 Directory Server)
>
> The above user will not have IPA-specific attributes.
>
> Can we use the Python Library, or CLI, to modify the account to
> IPA-ize it?
Is this an integration w
Hi:
Scenario:
1) User is created via LDAP call to IPA (i.e.the 389 Directory Server)
The above user will not have IPA-specific attributes.
Can we use the Python Library, or CLI, to modify the account to IPA-ize it?
Thanks.
___
Freeipa-users mailing l
12 matches
Mail list logo
