a

}�f*��-@s:dZd
dl
mZ
d
dlZd
dlZd
dlZd
dlZzd
dlm	Z	
Wn&e
yf


d
dlmZm
Z
m	Z	
Yn0d
dlmZm
Z

ejr�eZdZdd	�Zd
d�Zdd
�Zdd�Zdd�Zdd�Zdd�Zdd�Zejr�dd�Zdd�Zndd�Zdd�ZejGdd�d��
ZejGd d!�d!��
Z ejGd"d#�d#��
Z!ej"j#j$j%d$ej"j#j$j&d%ej"j#j$j'd&ej"j#j$j(d'ej"j#j$j)d(ej"j#j$j*d)ej"j#j$j+d*ej"j#j$j,d+ej"j#j$j-d,ej"j#j$j.d-ej"j#j$j/d.ej"j#j$j0d/ej"j#j$j1d0ej"j#j$j2d1ej"j#j$j3d2ej"j#j$j4d3ej"j#j$j5d4ej"j#j$j6d5ej"j#j$j7d6ej"�8d7�
d8ej"�8d9�
d:ej"�8d;�
d<iZ9dS)=a�2

Goal
----

To allow a Python programmer the ability to operate on DN's
(Distinguished Names) in a simple intuitive manner supporting all the
Pythonic mechanisms for manipulating objects such that the simple
majority case remains simple with simple code, yet the corner cases
are fully supported. With the result both simple and complex cases are
100% correct.

This is achieved with a fair of amount of syntax sugar which is best
described as "Do What I Mean" (i.e. DWIM). The class implementations
take simple expressions and internally convert them to their more
complex full definitions hiding much of the complexity from the
programmer.

Anatomy of a DN
---------------

Some definitions:

AVA
    An AVA is an Attribute Value Assertion. In more simple terms it's
    an attribute value pair typically expressed as attr=value
    (e.g. cn=Bob). Both the attr and value in an AVA when expressed in
    a string representation are subject to encoding rules.

RDN
    A RDN is a Relative Distinguished Name. A RDN is a non-empty set of
    AVA's. In the common case a RDN is single valued consisting of 1
    AVA (e.g. cn=Bob). But a RDN may be multi-valued consisting of
    more than one AVA. Because the RDN is a set of AVA's the AVA's are
    unordered when they appear in a multi-valued RDN. In the string
    representation of a RDN AVA's are separated by the plus sign (+).

DN
    A DN is a ordered sequence of 1 or more RDN's. In the string
    representation of a DN each RDN is separated by a comma (,)

Thus a DN is:

Sequence of set of <encoded attr, encoded value> pairs

The following are valid DN's

# 1 RDN with 1 AVA (e.g. cn=Bob)
RDN(AVA)

# 2 RDN's each with 1 AVA (e.g. cn=Bob,dc=redhat.com)
RDN(AVA),RDN(AVA)

# 2 RDN's the first RDN is multi-valued with 2 AVA's
# the second RDN is singled valued with 1 AVA
# (e.g. cn=Bob+ou=people,dc=redhat.com
RDN({AVA,AVA}),RDN(AVA)

Common programming mistakes
---------------------------

DN's present a pernicious problem for programmers. They appear to have
a very simple string format in the majority case, a sequence of
attr=value pairs separated by commas. For example:

dn='cn=Bob,ou=people,dc=redhat,dc=com'

As such there is a tendency to believe you can form DN's by simple
string manipulations such as:

dn='%s=%s' % ('cn','Bob') + ',ou=people,dc=redhat,dc=com'

Or to extract a attr & value by searching the string, for example:

attr=dn[0 : dn.find('=')]
value=dn[dn.find('=')+1 : dn.find(',')]

Or compare a value returned by an LDAP query to a known value:

if value == 'Bob'

All of these simple coding assumptions are WRONG and will FAIL when a
DN is not one of the simple DN's (simple DN's are probably the 95% of
all DN's). This is what makes DN handling pernicious. What works in
95% of the cases and is simple, fails for the 5% of DN's which are not
simple.

Examples of where the simple assumptions fail are:

* A RDN may be multi-valued

* A multi-valued RDN has no ordering on it's components

* Attr's and values must be UTF-8 encoded

* String representations of AVA's, RDN's and DN's must be completely UTF-8

* An attr or value may have reserved characters which must be escaped.

* Whitespace needs special handling

To complicate matters a bit more the RFC for the string representation
of DN's (RFC 4514) permits a variety of different syntax's each of
which can evaluate to exactly the same DN but have different string
representations. For example, the attr "r,w" which contains a reserved
character (the comma) can be encoded as a string in these different
ways:

'r\,w'          # backslash escape
'r\2cw'         # hexadecimal ascii escape
'#722C77'       # binary encoded

It should be clear a DN string may NOT be a simple string, rather a DN
string is ENCODED. For simple strings the encoding of the DN is
identical to the simple string value (this common case leads to
erroneous assumptions and bugs because it does not account for
encodings).

The openldap library we use at the client level uses the backslash
escape form. The LDAP server we use uses the hexadecimal ascii escape
form. Thus 'r,w' appears as 'r\,w' when sent from the client to the
LDAP server as part of a DN. But when it's returned as a DN from the
server in an LDAP search it's returned as 'r\2cw'. Any attempt to
compare 'r\,w' to 'r\2cw' for equality will fail despite the fact they
are indeed equal once decoded. Such a test fails because you're
comparing two different encodings of the same value. In MIME you
wouldn't expect the base64 encoding of a string to be equal to the
same string encoded as quoted-printable would you?

When you are comparing attrs or values which are part of a DN and
other string you MUST:

* Know if either of the strings have been encoded and make sure you're
  comparing only decoded components component-wise.

* Extract the component from the DN and decode it. You CANNOT decode
  the entire DN as a string and operate on it. Why? Consider a value
  with a comma embedded in it. For example:

  cn=r\2cw,cn=privilege

  Is a DN with 2 RDN components: cn=r,w followed by "cn=privilege"

  But if you decode the entire DN string as a whole you would get:

  cn=r,w,cn=privilege

  Which is a malformed DN with 3 RDN's, the 2nd RDN is invalid.

* Determine if a RDN is multi-valued, if so you must account
  for the fact each AVA component in the multi-valued RDN can appear
  in any order and still be equivalent. For example the following two
  RDN's are equal:

  cn=Bob+ou=people
  ou=people+cn=Bob

  In addition each AVA (cn=Bob & ou=people) needs to be
  INDEPENDENTLY decoded prior to comparing the unordered set of AVA's
  in the multi-valued RDN.

If you are trying to form a new DN or RDN from a raw string you cannot
simply do string concatenation or string formatting unless you ESCAPE
the components independently prior to concatenation, for example:

  base = 'dc=redhat,dc=com'
  value = 'r,w'
  dn = 'cn=%s,%s' % (value, base)

Will result in the malformed DN 'cn=r,w,dc=redhat,dc=com'

Syntax Sugar
------------

The majority of DN's have a simple string form:

attr=value,attr=value

We want the programmer to be able to create DN's, compare them, and
operate on their components as simply and concisely as possible so
the classes are implemented to provide a lot of syntax sugar.

The classes automatically handle UTF-8 <-> Unicode conversions. Every
attr and value which is returned from a class will be Unicode. Every
attr and value assigned into an object will be promoted to
Unicode. All string representations in RFC 4514 format will be UTF-8
and properly escaped. Thus at the "user" or "API" level every string
is Unicode with the single exception that the str() method returns RFC
compliant escaped UTF-8.

RDN's are assumed to be single-valued. If you need a multi-valued RDN
(an exception) you must explicitly create a multi-valued RDN.

Thus DN's are assumed to be a sequence of attr, value pairs, which is
equivalent to a sequence of RDN's. The attr and value in the pair MUST
be strings.

The DN and RDN constructors take a sequence, the constructor parses
the sequence to find items it knows about.

The DN constructor will accept in it's sequence:
  * tuple of 2 strings, converting it to an RDN
  * list of 2 strings, converting it to an RDN
  * a RDN object
  * a DN syntax string (e.g. 'cn=Bob,dc=redhat.com')

Note DN syntax strings should be avoided if possible when passing to a
constructor because they run afoul of the problems outlined above
which the DN, RDN & AVA classes are meant to overcome. But sometimes a
DN syntax string is all you have to work with. DN strings which come
from a LDAP library or server will be properly formed and it's safe to
use those. However DN strings provided via user input should be
treated suspiciously as they may be improperly formed. You can test
for this by passing the string to the DN constructor and see if it
throws an exception.

The sequence passed to the DN constructor takes each item in order,
produces one or more RDN's from it and appends those RDN in order to
its internal RDN sequence.

For example:

   DN(('cn', 'Bob'), ('dc', 'redhat.com'))

This is equivalent to the DN string:

    cn=Bob,dc=redhat.com

And is exactly equal to:

    DN(RDN(AVA('cn','Bob')),RDN(AVA('dc','redhat.com')))

The following are alternative syntax's which are all exactly
equivalent to the above example.

   DN(['cn', 'Bob'], ['dc', 'redhat.com'])
   DN(RDN('cn', 'Bob'), RDN('dc', 'redhat.com'))

You can provide a properly escaped string representation.

   DN('cn=Bob,dc=redhat.com')

You can mix and match any of the forms in the constructor parameter
list.

   DN(('cn', 'Bob'), 'dc=redhat.com')
   DN(('cn', 'Bob'), RDN('dc', 'redhat.com'))

AVA's have an attr and value property, thus if you have an AVA

# Get the attr and value
ava.attr  -> u'cn'
ava.value -> u'Bob'

# Set the attr and value
ava.attr  = 'cn'
ava.value = 'Bob'

Since RDN's are assumed to be single valued, exactly the same
behavior applies to an RDN. If the RDN is multi-valued then the attr
property returns the attr of the first AVA, likewise for the value.

# Get the attr and value
rdn.attr  -> u'cn'
rdn.value -> u'Bob'

# Set the attr and value
rdn.attr  = 'cn'
rdn.value = 'Bob'

Also RDN's can be indexed by name or position (see the RDN class doc
for details).

rdn['cn'] -> u'Bob'
rdn[0] -> AVA('cn', 'Bob')

A DN is a sequence of RDN's, as such any of Python's container
operators can be applied to a DN in a intuitive way.

# How many RDN's in a DN?
len(dn)

# WARNING, this a count of RDN's not how characters there are in the
# string representation the dn, instead that would be:
len(str(dn))

# Iterate over each RDN in a DN
for rdn in dn:

# Get the first RDN in a DN
dn[0] -> RDN('cn', 'Bob')

# Get the value of the first RDN in a DN
dn[0].value -> u'Bob'

# Get the value of the first RDN by indexing by attr name
dn['cn'] -> u'Bob'

# WARNING, when a string is used as an index key the FIRST RDN's value
# in the sequence whose attr matches the key is returned. Thus if you
# have a DN like this "cn=foo,cn=bar" then dn['cn'] will always return
# 'foo' even though there is another attr with the name 'cn'. This is
# almost always what the programmer wants. See the class doc for how
# you can override this default behavior and get a list of every value
# whose attr matches the key.

# Set the first RDN in the DN (all are equivalent)
dn[0] = ('cn', 'Bob')
dn[0] = ['cn', 'Bob']
dn[0] = RDN('cn', 'Bob')

dn[0].attr = 'cn'
dn[0].value = 'Bob'

# Get the first two RDN's using slices
dn[0:2]

# Get the last two RDN's using slices
dn[-2:]

# Get a list of all RDN's using slices
dn[:]

# Set the 2nd and 3rd RDN using slices (all are equivalent)
dn[1:3] = ('cn', 'Bob), ('dc', 'redhat.com')
dn[1:3] = RDN('cn', 'Bob), RDN('dc', 'redhat.com')

String representations and escapes:

# To get an RFC compliant string representation of a DN, RDN or AVA
# simply call str() on it or evaluate it in a string context.
str(dn) -> 'cn=Bob,dc=redhat.com'

# When working with attr's and values you do not have to worry about
# escapes, simply use the raw unescaped string in a natural fashion.

rdn = RDN('cn', 'r,w')

# Thus:
rdn.value == 'r,w' -> True

# But:
str(rdn) == 'cn=r,w' -> False
# Because:
str(rdn) -> 'cn=r\2cw' or 'cn='r\,w' # depending on the underlying LDAP library

Equality and Comparing:

# All DN's, RDN's and AVA's support equality testing in an intuitive
# manner.
dn1 = DN(('cn', 'Bob'))
dn2 = DN(RDN('cn', 'Bob'))
dn1 == dn2 -> True
dn1[0] == dn2[0] -> True
dn1[0].value = 'Bobby'
dn1 == dn2 -> False

DN objects implement startswith(), endswith() and the "in" membership
operator. You may pass a DN or RDN object to these. Examples:

if dn.endswith(base_dn):
if dn.startswith(rdn1):
if container_dn in dn:

# See the class doc for how DN's, RDN's and AVA's compare
# (e.g. cmp()). The general rule is for objects supporting multiple
# values first their lengths are compared, then if the lengths match
# the respective components of each are pair-wise compared until one
# is discovered to be  non-equal. The comparison is case insensitive.

Concatenation, In-Place Addition, Insertion:

# DN's and RDN's can be concatenated.
# Return a new DN by appending the RDN's of dn2 to dn1
dn3 = dn1 + dn2

# Append a RDN to DN's RDN sequence (all are equivalent)
dn += ('cn', 'Bob')
dn += RDN('cn', 'Bob')

# Append a DN to an existing DN
dn1 += dn2

# Prepend a RDN to an existing DN
dn1.insert(0, RDN('cn', 'Bob'))

Finally see the unittest for a more complete set of ways you can
manipulate these objects.

Immutability
------------

All the class types are immutable.
As with other immutable types (such as str and int), you must not rely on
the object identity operator ("is") for comparisons.

It is possible to "copy" an object by passing an object of the same type
to the constructor. The result may share underlying structure.

�)
�print_functionN)
�DECODING_ERROR)�str2dn�dn2strr)rr)�AVA�RDN�DNcCsN|
|kr|}
n|
d
kr*|
|7}
|
d
kr*d
}
|d
krF||7}|d
krFd
}||
fS)z&helper to fixup start/end slice valuesr
�)�start�end�lengthr	r	�0/usr/lib/python3.9/site-packages/ipapython/dn.py�_adjust_indices�
s







rc

CsTtj
rt|t�rtd
|�
�
n2t|t�s6tt|�
�
}ntjrPt|t�rP|�	d�
}|S)Nzexpected str, got bytes: %r�utf-8)
�six�PY3�
isinstance�bytes�	TypeError�str�
val_encode�PY2�unicode�encode)
�valr	r	r
�_normalize_ava_input�
s








rc
CsRzt|�
d
�
�
}
Wnty0


td|�
�
Yn0t|
�
dkrJtd|�
�
|
dS)Nrzmalformed AVA string = "%s"�
z multiple RDN's specified by "%s"r
)rrr�
ValueError�len)�value�rdnsr	r	r
�str2rdn�
s






r!cGs�d
}
t|�
}|dkr|}
n�|dkr>t
|d�
t
|d�
dg}
n�|dkr�|d}t|t�rb|��}
q�t|ttf�r�t|�
dkr�td|�
�
t
|d�
t
|d�
dg}
q�t|t�r�t	|�
}t|�
dkr�t
d|�
�
t|d�
}
q�t
d|jj�
�
nt
d	�
�
|
S)
a�

    Get AVA from args in open ldap format(raw). Optimized for construction
    from openldap format.

    Allowed formats of argument list:
    1) three args - open ldap format (attr and value have to be utf-8 encoded):
        a) ['attr', 'value', 0]
    2) two args:
        a) ['attr', 'value']
    3) one arg:
        a) [('attr', 'value')]
        b) [['attr', 'value']]
        c) [AVA(..)]
        d) ['attr=value']
    N��r
rz(tuple or list must be 2-valued, not "%s"z multiple AVA's specified by "%s"zMwith 1 argument, argument must be str, unicode, tuple or list, got %s insteadz(invalid number of arguments. 1-3 allowed)
rrrr�to_openldap�tuple�listrrr!r�	__class__�__name__)�args�ava�
l�arg�rdnr	r	r
�get_ava�
s0





















�
r.c

Cs t|�
d
k
rdS|j
td�

dS)Nr)
�key)r�sort�ava_key�
r-r	r	r
�	sort_avas
s


r3c

Cs|d
��|d��fS�Nr
r)
�lower)
r*r	r	r
r1s
r1cCs0t|�
}t|
�
}||krd
S||kr(dSdSdS)Nr
���r)
�rdn_key)�
a�
bZkey_aZkey_br	r	r
�cmp_rdnss





r:c

Cst|�
f
t
d
d�|D�
�
S)Nc
ss|]}
t|
�
V
qdS�
N)
r1)�.0�
kr	r	r
�	<genexpr> �zrdn_key.<locals>.<genexpr>)rr%r2r	r	r
r7s
r7c

Cs
|�d
�
S�Nr)
r�
�
sr	r	r
r%s
rc

Cs
|�d
�
Sr@)
�decoderAr	r	r
�
val_decode(s
rDc

Cst|t
�rtd
|�
�
|S)Nzexpected str, got bytes: %s)rrrrAr	r	r
r,s



c


Cs|Sr;r	rAr	r	r
rD1s
c@s�eZ
dZd
Zdd�Zdd�Zdd�Zee�
Zdd	�Z	d
d�Z
ee	�
Zdd
�Zdd�Z
dd�Zdd�Zdd�Zdd�Zdd�Zdd�ZdS)ra
    AVA(arg0, ...)

    An AVA is an LDAP Attribute Value Assertion. It is convenient to think of
    AVA's as a <attr,value> pair. AVA's are members of RDN's (Relative
    Distinguished Name).

    The AVA constructor is passed a sequence of args and a set of
    keyword parameters used for configuration.

    The arg sequence may be:

    1) With 2 arguments, the first argument will be the attr, the 2nd
    the value. Each argument must be scalar convertable to unicode.

    2) With a sigle list or tuple argument containing exactly 2 items.
    Each item must be scalar convertable to unicode.

    3) With a single string (or unicode) argument, in this case the string will
    be interpretted using the DN syntax described in RFC 4514 to yield a AVA
    <attr,value> pair. The parsing recognizes the DN syntax escaping rules.

    For example:

    ava = AVA('cn', 'Bob')	# case 1: two strings
    ava = AVA(('cn', 'Bob'))    # case 2: 2-valued tuple
    ava = AVA(['cn', 'Bob'])    # case 2: 2-valued list
    ava = AVA('cn=Bob')         # case 3: DN syntax

    AVA object have two properties for accessing their data:

    attr:  the attribute name, cn in our exmaple
    value: the attribute's value, Bob in our example

    When attr and value are returned they will always be unicode. When
    attr or value are set they will be promoted to unicode.

    AVA objects support indexing by name, e.g.

    ava['cn']

    returns the value (Bob in our example). If the index does key does not match
    the attr then a KeyError will be raised.

    AVA objects support equality testing and comparsion (e.g. cmp()). When they
    are compared the attr is compared first, if the 2 attr's are equal then the
    values are compared. The comparison is case insensitive (because attr's map
    to numeric OID's and their values derive from from the 'name' atribute type
    (OID 2.5.4.41) whose EQUALITY MATCH RULE is caseIgnoreMatch.

    The str method of an AVA returns the string representation in RFC 4514 DN
    syntax with proper escaping.
    c
Gst|
�|_
dSr;)r.�_ava)�selfr)r	r	r
�__init__ls
zAVA.__init__c

Cst|j
d
�
S)Nr
�rDrE�
rFr	r	r
�	_get_attros
z
AVA._get_attrc
CsLzt|
�
|j
d
<Wn4tyF
}
ztd|
|f�
�
WYd}~n
d}~00dS)Nr
zunable to convert attr "%s": %s�rrE�	Exceptionr)rF�new_attr�
er	r	r
�	_set_attrrs



z
AVA._set_attrc

Cst|j
d
�
S)NrrHrIr	r	r
�
_get_valuezs
zAVA._get_valuec
CsLzt|
�
|j
d
<Wn4tyF
}
ztd|
|f�
�
WYd}~n
d}~00dS)Nrz unable to convert value "%s": %srK)rF�	new_valuerNr	r	r
�
_set_value}s



zAVA._set_valuec

Cs
t|j
�
Sr;)r&rErIr	r	r
r$�s
zAVA.to_openldapc

Cst|�
�g
g
�
Sr;�rr$rIr	r	r
�__str__�s
zAVA.__str__c

Csd
|j|j
j|��fS�Nz%s.%s('%s')��
__module__r'r(rTrIr	r	r
�__repr__�s
zAVA.__repr__cCsD|
d
kr|jS|
dkr|j
S|
|jkr,|j
Std|
|��f�
�
dS)Nr
r�"%s" not found in %s)�attrr�KeyErrorrT)rFr/r	r	r
�__getitem__�s





zAVA.__getitem__c

Cstt
|�
���
Sr;��hashrr5rIr	r	r
�__hash__�szAVA.__hash__cCsVt|
t
�r4zt|
�
}|�|�
WSty2


Yd
S0t|
t�sBd
St|j�
t|
j�
kS)a
        The attr comparison is case insensitive because attr is
        really an LDAP attribute type which means it's specified with
        an OID (dotted number) and not a string. Since OID's are
        numeric the human readable name which maps to the OID is not
        significant in case.

        The value comparison is also case insensitive because the all
        attribute types used in a DN are derived from the 'name'
        atribute type (OID 2.5.4.41) whose EQUALITY MATCH RULE is
        caseIgnoreMatch.
        F)rrr�__eq__rLr1rE)rF�otherZ	other_avar	r	r
r`�s







z
AVA.__eq__cCs|�|
�
Sr;�
r`�rFrar	r	r
�__ne__�s
z
AVA.__ne__cCs.t|
t
�std
|
jj�
�
t|j�
t|
j�
kS)z>comparison is case insensitive, see __eq__ doc for explanationzexpected AVA but got %s)rrrr'r(r1rErcr	r	r
�__lt__�s

z
AVA.__lt__N)r(rW�__qualname__�__doc__rGrJrO�propertyrZrPrRrr$rTrXr\r_r`rdrer	r	r	r
r5s 5	rc@s�eZ
dZd
ZeZdd�Zd*dd�
Zdd�Zd	d
�Z	dd�Z
d
d�Zdd�Zdd�Z
dd�Zdd�Zdd�Zdd�Zee�
Zdd�Zdd�Zee�
Zdd �Zd!d"�Zd#d$�Zd%d&�Zd'd(�Zd)S)+ra�
    RDN(arg0, ...)

    An RDN is a LDAP Relative Distinguished Name. RDN's are members of DN's
    (Distinguished Name). An RDN contains 1 or more AVA's. If the RDN contains
    more than one AVA it is said to be a multi-valued RDN. When an RDN is
    multi-valued the AVA's are unorderd comprising a set. However this
    implementation orders the AVA's according to the AVA comparison function to
    make equality and comparison testing easier. Think of this a canonical
    normalization (however LDAP does not impose any ordering on multiple AVA's
    within an RDN). Single valued RDN's are the norm and thus the RDN
    constructor has simple syntax for them.

    The RDN constructor is passed a sequence of args and a set of
    keyword parameters used for configuration.

    The constructor iterates though the sequence and adds AVA's to the RDN.

    The arg sequence may be:

    * A 2-valued tuple or list denotes the <attr,value> pair of an AVA. The
    first member is the attr and the second member is the value, both members
    must be strings (or unicode). The tuple or list is passed to the AVA
    constructor and the resulting AVA is added to the RDN. Multiple tuples or
    lists may appear in the argument list, each adds one additional AVA to the
    RDN.

    * A single string (or unicode) argument, in this case the string will
    be interpretted using the DN syntax described in RFC 4514 to yield one or
    more AVA <attr,value> pairs. The parsing recognizes the DN syntax escaping
    rules.

    * A AVA object, the AVA will be copied into the new RDN respecting
      the constructors keyword configuration parameters.

    * A RDN object, the AVA's in the RDN are copied into the new RDN
      respecting the constructors keyword configuration parameters.

    Single AVA Examples:

    RDN(('cn', 'Bob'))                  # tuple yields 1 AVA
    RDN('cn=Bob')                       # DN syntax with 1 AVA
    RDN(AVA('cn', 'Bob'))               # AVA object adds 1 AVA

    Multiple AVA Examples:

    RDN(('cn', 'Bob'),('ou', 'people')) # 2 tuples yields 2 AVA's
    RDN('cn=Bob+ou=people')             # DN syntax with 2 AVA's
    RDN(AVA('cn', 'Bob'),AVA('ou', 'people')) # 2 AVA objects adds 2 AVA's
    RDN(('cn', 'Bob'), 'ou=people')     # 2 args, 1st tuple forms 1 AVA,
                                        # 2nd DN syntax string adds 1 AVA,
                                        # 2 AVA's in total

    Note: The RHS of a slice assignment is interpreted exactly in the
    same manner as the constructor argument list (see above examples).

    RDN objects support iteration over their AVA members. You can iterate all
    AVA members via any Python iteration syntax. RDN objects support full Python
    indexing using bracket [] notation. Examples:

    len(rdn)            # return the number of AVA's
    rdn[0]              # indexing the first AVA
    rdn['cn']           # index by AVA attr, returns AVA value
    for ava in rdn:     # iterate over each AVA
    rdn[:]              # a slice, in this case a copy of each AVA

    WARNING: When indexing by attr (e.g. rdn['cn']) there is a possibility more
    than one AVA has the same attr name as the index key. The default behavior
    is to return the value of the first AVA whose attr matches the index
    key.

    RDN objects support the AVA attr and value properties as another programmer
    convenience because the vast majority of RDN's are single valued. The attr
    and value properties return the attr and value properties of the first AVA
    in the RDN, for example:

    rdn = RDN(('cn', 'Bob')) # rdn has 1 AVA whose attr == 'cn' and value == 'Bob'
    len(rdn) -> 1
    rdn.attr -> u'cn'      # exactly equivalent to rdn[0].attr
    rdn.value -> u'Bob'    # exactly equivalent to rdn[0].value

    When attr and value are returned they will always be unicode. When
    attr or value are set they will be promoted to unicode.

    If an RDN is multi-valued the attr and value properties still return only
    the first AVA's properties, programmer beware! Recall the AVA's in the RDN
    are sorted according the to AVA collating semantics.

    RDN objects support equality testing and comparison. See AVA for the
    definition of the comparison method.

    RDN objects support concatenation and addition with other RDN's or AVA's

    rdn1 + rdn2 # yields a new RDN object with the contents of each RDN.
    rdn1 + ava1 # yields a new RDN object with the contents of rdn1 and ava1

    RDN objects can add AVA's objects via in-place addition.

    rdn1 += rdn2 # rdn1 now contains the sum of rdn1 and rdn2
    rdn1 += ava1 # rdn1 has ava1 added to it.

    The str method of an RDN returns the string representation in RFC 4514 DN
    syntax with proper escaping.
    c
Os|�|
|�
d
d��|_dS)N�rawF)�_avas_from_sequence�get�_avas�rFr)�kwdsr	r	r
rG7s
zRDN.__init__FcCs�g}d
}t|
�
}|r|
}np|dkrBt
|
d
t�rBt|
d
�
}d}nH|dkrft
|
d
t�rf|
d
��}n$|d
kr�d}|
D]}|�t|�
�

qv|r�t|�

|Sr4)	rrrr!rr$�appendr.r3)rFr)riZavasr0Z	ava_countr,r	r	r
rj:s"















zRDN._avas_from_sequencec

Csd
d�|jD�
S)Nc
Ssg|]}
t|
�
�qSr	�
r&�r<r8r	r	r
�
<listcomp>Or?z#RDN.to_openldap.<locals>.<listcomp>)
rlrIr	r	r
r$Ns
zRDN.to_openldapc

Cst|�
�g
�
Sr;rSrIr	r	r
rTQs
zRDN.__str__c

Csd
|j|j
j|��fSrUrVrIr	r	r
rXTs
zRDN.__repr__cCs
|j|
�Sr;)
�AVA_type�rFr*r	r	r
�_get_avaWs
zRDN._get_avac
cs|jD]}
|�
|
�
V
qdSr;)rlrurtr	r	r
�_nextZs


z	RDN._nextc

Cs|��Sr;�
rvrIr	r	r
�__iter__^s
zRDN.__iter__c

Cs
t|j
�
Sr;)rrlrIr	r	r
�__len__as
zRDN.__len__cs�t|
t
�r���j|
�
St|
t�r<�f
d
d��j|
D�
St|
t�r��jD]$}|
t|d�
krLt|d�

SqLtd|
���f�
�
nt	d|
j
j�
�
dS)Nc
sg|]}
��|
�
�qSr	)
ru�r<r*rIr	r
rrhr?z#RDN.__getitem__.<locals>.<listcomp>r
rrYzKunsupported type for RDN indexing, must be int, basestring or slice; not %s)r�intrurl�slicerrDr[rTrr'r()rFr/r*r	rIr
r\ds













�zRDN.__getitem__c

Cs(t|j
�
d
krtd�
�
t|j
d
d
�
S�Nr
�No AVA's in this RDN�rrl�
IndexErrorrDrIr	r	r
rJrs


z
RDN._get_attrcCs0t|j
�
d
krtd�
�
tt|
�
�
|j
d
d
<dSr}�rrlr�rr)rFrMr	r	r
rOws

z
RDN._set_attrc

Cs(t|j
�
d
krtd�
�
t|j
d
d�
S�Nr
r~rrrIr	r	r
rPs


zRDN._get_valuecCs0t|j
�
d
krtd�
�
tt|
�
�
|j
d
d<dSr�r�)rFrQr	r	r
rR�s


zRDN._set_valuec

Cstt
|�
���
Sr;r]rIr	r	r
r_�szRDN.__hash__cCsVt|
t
�r4zt|
�
}|�|�
WSty2


Yd
S0t|
t�sBd
St|j�
t|
j�
kS)NF)rrrr`rLr7rl)rFraZ	other_rdnr	r	r
r`�s







z
RDN.__eq__cCs|�|
�
Sr;rbrcr	r	r
rd�s
z
RDN.__ne__cCs.t|
t
�std
|
jj�
�
t|j�
t|
j�
kS)Nzexpected RDN but got %s)rrrr'r(r7rlrcr	r	r
re�s


z
RDN.__lt__cCs�|�|�
}t
|
t�r@|
jD]"}|j�|d
|d|df�

qnlt
|
t�r\|j�|
���

nPt
|
t�r�|�|
�
}|jD]"}|j�|d
|d|df�

qvntd|
jj	�
�
t
|j�

|S)Nr
rr#z*expected RDN, AVA or basestring but got %s)r'rrrlrorr$rrr(r3)rFra�resultr*r-r	r	r
�__add__�s






"









"

zRDN.__add__N)
F)r(rWrfrgrrsrGrjr$rTrXrurvrxryr\rJrOrhrZrPrRrr_r`rdrer�r	r	r	r
r�s.i
	rc@s
eZ
dZd
ZeZeZdd�Zd<dd�
Z	dd�Z
d	d
�Zdd�Zd
d�Z
dd�Zdd�Zdd�Zdd�Zdd�Zdd�Zdd�Zdd�Zdd �Zd!d"�Zd#d$�Zd%d&�Zd'd(�Zd)d*�Zd+ejfd,d-�
Zd+ejfd.d/�
Zd0d1�Z d2d3�Z!d=d4d5�
Z"d>d6d7�
Z#d?d8d9�
Z$d@d:d;�
Z%dS)Ara�
    DN(arg0, ...)

    A DN is a LDAP Distinguished Name. A DN is an ordered sequence of RDN's.

    The DN constructor is passed a sequence of args and a set of
    keyword parameters used for configuration. normalize means the
    attr and value will be converted to lower case.

    The constructor iterates through the sequence and adds the RDN's
    it finds in order to the DN object. Each item in the sequence may
    be:

    * A 2-valued tuple or list. The first member is the attr and the
      second member is the value of an RDN, both members must be
      strings (or unicode). The tuple or list is passed to the RDN
      constructor and the resulting RDN is appended to the
      DN. Multiple tuples or lists may appear in the argument list,
      each adds one additional RDN to the DN.

    * A single string (or unicode) argument, in this case the string
      will be interpretted using the DN syntax described in RFC 4514
      to yield one or more RDN's which will be appended in order to
      the DN. The parsing recognizes the DN syntax escaping rules.

    * A single ``cryptography.x509.name.Name`` object.

    * A RDN object, the RDN will copied respecting the constructors
      keyword configuration parameters and appended in order.

    * A DN object, the RDN's in the DN are copied respecting the
      constructors keyword configuration parameters and appended in
      order.

    Single DN Examples:

    DN(('cn', 'Bob'))                   # tuple yields 1 RDN
    DN(['cn', 'Bob'])                   # list yields 1 RDN
    DN('cn=Bob')                        # DN syntax with 1 RDN
    DN(RDN('cn', 'Bob'))                # RDN object adds 1 RDN

    Multiple RDN Examples:

    DN(('cn', 'Bob'),('ou', 'people'))  # 2 tuples yields 2 RDN's
                                        # 2 RDN's total
    DN('cn=Bob,ou=people')              # DN syntax with 2 RDN's
                                        # 2 RDN's total
    DN(RDN('cn', 'Bob'),RDN('ou', 'people')) # 2 RDN objects
                                        # 2 RDN's total
    DN(('cn', 'Bob'), "ou=people')      # 1st tuple adds 1 RDN
                                        # 2nd DN syntax string adds 1 RDN
                                        # 2 RDN's total
    base_dn = DN('dc=redhat,dc=com')
    container_dn = DN('cn=sudorules,cn=sudo')
    DN(('cn', 'Bob'), container_dn, base_dn)
                                        # 1st arg adds 1 RDN, cn=Bob
                                        # 2nd arg adds 2 RDN's, cn=sudorules,cn=sudo
                                        # 3rd arg adds 2 RDN's, dc=redhat,dc=com
                                        # 5 RDN's total


    Note: The RHS of a slice assignment is interpreted exactly in the
    same manner as the constructor argument list (see above examples).

    DN objects support iteration over their RDN members. You can iterate all
    RDN members via any Python iteration syntax. DN objects support full Python
    indexing using bracket [] notation. Examples:

    len(rdn)            # return the number of RDN's
    rdn[0]              # indexing the first RDN
    rdn['cn']           # index by RDN attr, returns RDN value
    for ava in rdn:     # iterate over each RDN
    rdn[:]              # a slice, in this case a copy of each RDN

    WARNING: When indexing by attr (e.g. dn['cn']) there is a
    possibility more than one RDN has the same attr name as the index
    key. The default behavior is to return the value of the first RDN
    whose attr matches the index key. If it's important the attr
    belong to a specific RDN (e.g. the first) then this is the
    suggested construct:

        try:
            cn = dn[0]['cn']
        except (IndexError, KeyError):
            raise ValueError("dn '%s' missing expected cn as first attribute" % dn)

    The IndexError catches a DN which does not have the expected
    number of RDN's and the KeyError catches the case where the
    indexed RDN does not have the expected attr.

    DN object support slices.

    # Get the first two RDN's using slices
    dn[0:2]

    # Get the last two RDN's using slices
    dn[-2:]

    # Get a list of all RDN's using slices
    dn[:]

    # Set the 2nd and 3rd RDN using slices (all are equivalent)
    dn[1:3] = ('cn', 'Bob'), ('dc', 'redhat.com')
    dn[1:3] = [['cn', 'Bob'], ['dc', 'redhat.com']]
    dn[1:3] = RDN('cn', 'Bob'), RDN('dc', 'redhat.com')

    DN objects support the insert operation.

    dn.insert(i,x) is exactly equivalent to dn[i:i] = [x], thus the following
    are all equivalent:

    dn.insert(i, ('cn','Bob'))
    dn.insert(i, ['cn','Bob'])
    dn.insert(i, RDN(('cn','Bob')))
    dn[i:i] = [('cn','Bob')]

    DN objects support equality testing and comparison. See RDN for the
    definition of the comparison method.

    DN objects implement startswith(), endswith() and the "in" membership
    operator. You may pass a DN or RDN object to these. Examples:

    # Test if dn ends with the contents of base_dn
    if dn.endswith(base_dn):
    # Test if dn starts with a rdn
    if dn.startswith(rdn1):
    # Test if a container is present in a dn
    if container_dn in dn:

    DN objects support concatenation and addition with other DN's or RDN's
    or strings (interpreted as RFC 4514 DN syntax).

    # yields a new DN object with the RDN's of dn2 appended to the RDN's of dn1
    dn1 + dn2

    # yields a new DN object with the rdn1 appended to the RDN's of dn1
    dn1 + rdn1

    DN objects can add RDN's objects via in-place addition.

    dn1 += dn2  # dn2 RDN's are appended to the dn1's RDN's
    dn1 += rdn1 # dn1 has rdn appended to its RDN's
    dn1 += "dc=redhat.com" # string is converted to DN, then appended

    The str method of an DN returns the string representation in RFC 4514 DN
    syntax with proper escaping.
    c
Os|�|
�
|_
dSr;)�_rdns_from_sequencer rmr	r	r
rGXs
zDN.__init__NcCs|
s
|j}
d
d�|
D�
S)Nc
Ssg|]}
dd
�|
D�
�qS)c
Ssg|]}
t|
�
�qSr	rprqr	r	r
rr^r?z,DN._copy_rdns.<locals>.<listcomp>.<listcomp>r	�r<r-r	r	r
rr^r?z!DN._copy_rdns.<locals>.<listcomp>)
r )rFr r	r	r
�
_copy_rdns[s


z
DN._copy_rdnscCs�t|
t
�r\zt|
t
�rt|
�
}
t|
�
}WntyF


td
|
�
�
Yn0|D]}t|�

qLn�t|
t�rp|
��}n�t|
t	t
tf�r�t|
�
}|g
g
}nbt|
t
�r�|
��g
}nLt|
tjjj�r�t
tdd�|
jD�
�
�
}|D]}t|�

q�ntdt|
�
�
�
|S)Nzmalformed RDN string = "%s"c
Ssg|]}
dd
�|
D�
�qS)c
Ss&g|]}
tt
�|
j|
jj�|
j��qSr	)r.�ATTR_NAME_BY_OIDrk�oidZ
dotted_stringrrzr	r	r
rrss
�

�z2DN._rdns_from_value.<locals>.<listcomp>.<listcomp>r	r�r	r	r
rrrs��z'DN._rdns_from_value.<locals>.<listcomp>z<must be str, unicode, tuple, Name, RDN or DN, got %s instead)rrrrrrr3rr�r%r&rr.rr$�cryptography�x509�name�Name�reversedr r�type)rFrr r-r*r	r	r
�_rdns_from_value`s8
























�



��zDN._rdns_from_valuecCs&g}|
D]}|�|�
}|�
|�

q|Sr;)r��extend)rF�seqr �itemr-r	r	r
r��s





zDN._rdns_from_sequencec
Cs|Sr;r	)rF�memor	r	r
�__deepcopy__�s
zDN.__deepcopy__cCs|j|
id
di
�
�
S)NriT)
�RDN_type�rFr-r	r	r
�_get_rdn�s
zDN._get_rdnc

Cs
t|j
�
Sr;)rr rIr	r	r
�	ldap_text�s
zDN.ldap_textc

Cstt
|j�
�
Sr;)rr�r rIr	r	r
�	x500_text�s
zDN.x500_textc

Cs|��Sr;)
r�rIr	r	r
rT�s
z
DN.__str__c

Csd
|j|j
j|��fSrUrVrIr	r	r
rX�s
zDN.__repr__c
cs|jD]}
|�
|
�
V
qdSr;)r r�r�r	r	r
rv�s


zDN._nextc

Cs|��Sr;rwrIr	r	r
rx�s
zDN.__iter__c

Cs
t|j
�
Sr;)rr rIr	r	r
ry�s
z
DN.__len__cCs�t|
t
�r|�|j|
�
St|
t�rD|j}|�|�
}|j|
|_|St|
t�r�|jD]2}|D](}|
t|d
�
kr\t|d�


Sq\qTt	d|
|�
�f�
�
ntd|
jj�
�
dS)Nr
rrYzJunsupported type for DN indexing, must be int, basestring or slice; not %s)
rr{r�r r|r'�__new__rrDr[rTrr()rFr/�clsZnew_dnr-r*r	r	r
r\�s 


















�zDN.__getitem__c
Cs"d
�dd�|j
D�
�
}
t|
���
S)Nz;,c
Ss g|]}
d�d
d�|
D�
�
�qS)z++c
Ss$g|]\}
}}d�|
|pd
f�
�qS)z==��
�join)r<ZatypeZavalueZ_dummyr	r	r
rr�s�z*DN.__hash__.<locals>.<listcomp>.<listcomp>r�r�r	r	r
rr�s�
�zDN.__hash__.<locals>.<listcomp>)r�r r^r5)rFZstr_dnr	r	r
r_�s
�zDN.__hash__cCsrt|
t
ttf�r:zt|
�
}|�|�
WSty8


Yd
S0t|
t�sHd
St|�
t|
�
kr\d
S|�|
dt|�
�dkS)NFr
)	rrrrrr`rLr�
_cmp_sequence)rFraZother_dnr	r	r
r`�s







z	DN.__eq__cCs|�|
�
Sr;rbrcr	r	r
rd�s
z	DN.__ne__cCsPt|
t
�std
|
jj�
�
t|�
t|
�
kr:t|�
t|
�
kS|�|
dt|�
�dkS)N�expected DN but got %sr
)rrrr'r(rr�rcr	r	r
re�s




z	DN.__lt__cCsH|}d
}||krDt|j
||
j
|�}|d
kr2|S|d7}|d7}qd
Sr4)r:r )rF�patternZ
self_start�pat_lenZself_idxZpat_idx�
rr	r	r
r��s









zDN._cmp_sequencecCs|�||
�Sr;)
r'rcr	r	r
r��s
z
DN.__add__r
cCs>t|
t
�r.|
D]}|�|||d
�r
dSqdS|�|
||d
�S)a4

        Return True if the dn starts with the specified prefix (either a DN or
        RDN object), False otherwise.  With optional start, test dn beginning at
        that position.  With optional end, stop comparing dn at that position.
        prefix can also be a tuple of dn's or rdn's to try.
        r6TF�rr%�
_tailmatch)rF�prefixr
r�patr	r	r
�
startswith�s




z
DN.startswithcCs>t|
t
�r.|
D]}|�|||d
�r
dSqdS|�|
||d
�S)a.

        Return True if dn ends with the specified suffix (either a DN or RDN
        object), False otherwise.  With optional start, test dn beginning at
        that position.  With optional end, stop comparing dn at that position.
        suffix can also be a tuple of dn's or rdn's to try.
        rTFr�)rF�suffixr
rr�r	r	r
�endswiths




zDN.endswithcCs�t|
t
�rt|
�
}
t|
t�r&t|
�
}ntd
|
jj�
�
t|�
}t|||�\}}|dkrh|||kr�dSn,|||ks|||kr�dS|||kr�||}|||kr�|�|
||�SdS)z�
        Matches the end (direction >= 0) or start (direction < 0) of self
        against pattern (either a DN or RDN), using the start and end
        arguments. Returns 0 if not found and 1 if found.
        �expected DN or RDN but got %sr
)	rrrrrr'r(rr�)rFr�r
r�	directionr��self_lenr	r	r
r�s"











z
DN._tailmatchcCsxt|
t
�rt|
�
}
t|
t�rdt|
�
}t|�
|}d
}||k
r`|�|
||�}|d
krVdS|d7}q4dStd|
jj�
�
dS)z[Return the outcome of the test other in self.

        Note the reversed operands.
        r
TrFr�N)rrrrr�rr'r()rFraZ	other_lenr�
ir�r	r	r
�__contains__3s
















�zDN.__contains__c	Cs�t|
t
�rt|
�
}ntd
|
jj�
�
t|�
}|dur8d}|durD|}t|||�\}}|}t|||�}||k
r�|�|
||�}|dkr�|S|d7}qfdS)a


        Return the lowest index in the DN where pattern DN is found,
        such that pattern is contained in the range [start, end]. Optional
        arguments start and end are interpreted as in slice notation. Return
        -1 if pattern is not found.
        r�Nr
rr6)	rrrrr'r(r�maxr��	rFr�r
rr�r�r��stopr�r	r	r
�findIs"












zDN.findcCs"|�|
||�}|d
krt
d�
�
|S)zQ
        Like find() but raise ValueError when the pattern is not found.
        r6�pattern not found)r�r�rFr�r
rr�r	r	r
�indexjs


zDN.indexc	Cs�t|
t
�rt|
�
}ntd
|
jj�
�
t|�
}|dur8d}|durD|}t|||�\}}t|t|||��}|}||kr�|�	|
||�}|dkr�|S|d8}qldS)a

        Return the highest index in the DN where pattern DN is found,
        such that pattern is contained in the range [start, end]. Optional
        arguments start and end are interpreted as in slice notation. Return
        -1 if pattern is not found.
        r�Nr
rr6)
rrrrr'r(rr��minr�r�r	r	r
�rfindts"












zDN.rfindcCs"|�|
||�}|d
krt
d�
�
|S)zR
        Like rfind() but raise ValueError when the pattern is not found.
        r6r�)r�rr�r	r	r
�rindex�s


z	DN.rindex)
N)NN)NN)NN)NN)&r(rWrfrgrrsrr�rGr�r�r�r�r�r�r�rTrXrvrxryr\r_r`rdrer�r��sys�maxsizer�r�r�r�r�r�r�r�r	r	r	r
r�s@

 	 
!


 rZCN�
C�
LZST�
OZOUZserialNumberZSNZ	givenName�titleZgenerationQualifierZdnQualifierZ	pseudonymZDC�
EZincorporationCountryZincorporationLocalityZincorporationStateZbusinessCategoryz2.5.4.9ZSTREETz2.5.4.17Z
postalCodez0.9.2342.19200300.100.1.1ZUID):rgZ
__future__rr��	functoolsZcryptography.x509r�rZldapr�ImportErrorZipapython.dn_ctypesrrZldap.dnrrr�__all__rrr!r.r3r1r:r7rrrD�total_orderingrrrr�r�ZNameOIDZCOMMON_NAMEZCOUNTRY_NAMEZ
LOCALITY_NAMEZSTATE_OR_PROVINCE_NAMEZORGANIZATION_NAMEZORGANIZATIONAL_UNIT_NAMEZ
SERIAL_NUMBERZSURNAMEZ
GIVEN_NAMEZTITLEZGENERATION_QUALIFIERZDN_QUALIFIERZ	PSEUDONYMZDOMAIN_COMPONENTZ
EMAIL_ADDRESSZJURISDICTION_COUNTRY_NAMEZJURISDICTION_LOCALITY_NAMEZ#JURISDICTION_STATE_OR_PROVINCE_NAMEZBUSINESS_CATEGORYZObjectIdentifierr�r	r	r	r
�<module>s�







+


u
c


























�