Tag: Networking, Networking / Home

Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
Home » Networking

  • Fwd: Why groupOfURLs is STRUTURAL?

    5 answers - 902 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Dear, list!
    I'm trying to implement dynamic posixGroup using dynlist overlay. The
    problem is that both posixGroup and URLs are STRUCTURAL object
    classes, i.e. do not stick together.
    dyngroup.schema states:
    "Dynamic Group schema (experimental), as defined by Netscape"
    I've checked schemas that come with Fedora Directory Server (FDS)
    (which itself originates from NetScape server, ASFAIK). In those
    schemas, URLs is not defined neither as STRUCTURAL nor as
    AUXILIARY:
    objectClasses: ( 2.16.840.1.113730.3.2.33 NAME 'URLs' DESC
    'Netscape defined objectclass' SUP top MUST ( cn ) MAY ( memberURL $
    businessCategory $ description $ o $ ou $ owner $ seeAlso ) XRIGIN
    'Netscape Directory Server' )
    My question is:
    Is there any reason that URLs objectclass is defined as
    STRUCTURAL and not as AUXILIARY?

  • No.1 | | 1287 bytes | |

    At 08:19 AM 9/19/2006, Hai Zaar wrote:
    >I'm trying to implement dynamic posixGroup using dynlist overlay. The
    >problem is that both posixGroup and URLs are STRUCTURAL object
    >classes, i.e. do not stick together.
    >
    >dyngroup.schema states:
    >"Dynamic Group schema (experimental), as defined by Netscape"
    >
    >I've checked schemas that come with Fedora Directory Server (FDS)
    >(which itself originates from NetScape server, ASFAIK). In those
    >schemas, URLs is not defined neither as STRUCTURAL nor as
    >AUXILIARY:

    Every object class is either structural, auxiliary, or abstract
    Where an object class description doesn't include a keyword
    indicating the kind, the kind defaults to structural. See RFC 4512.

    >objectClasses: ( 2.16.840.1.113730.3.2.33 NAME 'URLs' DESC
    >'Netscape defined objectclass' SUP top MUST ( cn ) MAY ( memberURL $
    >businessCategory $ description $ o $ ou $ owner $ seeAlso ) XRIGIN
    >'Netscape Directory Server' )

    This description is semantically equivalent to that provided in
    dynschema. That is, both describe the class as structural.
    -- Kurt

  • No.2 | | 324 bytes | |

    >
    This description is semantically equivalent to that provided in
    dynschema. That is, both describe the class as structural.
    Thank you for reply. Back to original problem:
    How can I implement "Dynamic posixGroup" - i.e. posixGroup with
    memberURL atributte evaluated by dynlist overlay.

    -- Kurt
    --

  • No.3 | | 708 bytes | |

    At 09:32 AM 9/19/2006, Hai Zaar wrote:
    >>This description is semantically equivalent to that provided in
    >>dynschema. That is, both describe the class as structural.
    >Thank you for reply. Back to original problem:
    >How can I implement "Dynamic posixGroup" - i.e. posixGroup with
    >memberURL atributte evaluated by dynlist overlay.

    IIRC, URLs is an alternative way of expressing a
    Names and/or UniqueNames. I don't believe
    it was intended to be used as an alterative way of expressing
    a posixGroup.

    You could code something similar by hacking on the dyngroup
    overlay.

    Kurt

  • No.4 | | 580 bytes | |

    Tue, Sep 19, 2006 at 07:32:12PM +0300, Hai Zaar wrote:
    >
    >This description is semantically equivalent to that provided in
    >dynschema. That is, both describe the class as structural.
    Thank you for reply. Back to original problem:
    How can I implement "Dynamic posixGroup" - i.e. posixGroup with
    memberURL atributte evaluated by dynlist overlay.

    You could hack your rfc2307 schema into rfc2307bis, where posixGroup is
    defined as AUXILIARY. Some distros already do this, and eventually it
    will be the norm.

  • No.5 | | 888 bytes | |

    Hai Zaar wrote:
    >>
    >This description is semantically equivalent to that provided in
    >dynschema. That is, both describe the class as structural.
    Thank you for reply. Back to original problem:
    How can I implement "Dynamic posixGroup" - i.e. posixGroup with
    memberURL atributte evaluated by dynlist overlay.
    Create an objectClass of your own which inherits from both posixGroup
    and URLs; or, since dynlist's dynamic objectClass is
    configurable, create your own class which inherits from posixGroup and
    has the memberURL member.

    p.

    Ing. Pierangelo Masarati
    LDAP Core Team

    SysNet s.n.c.
    Via Dossi, 8 - 27100 Pavia - ITALIA
    http://www.sys-net.it

    : +39.02.23998309
    Mobile: +39.333.4963172
    Email: pierangelo.masarati (AT) sys-net (DOT) it

Re: Fwd: Why groupOfURLs is STRUTURAL?


max 4000 letters.
Your nickname that display:
In order to stop the spam: 9 + 9 =
QUESTION ON "Networking"

EMSDN.COM