[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2693.0. "X.500 .. Surname with "/"" by DJOV09::ABREU () Thu May 22 1997 15:39

    	Hi,
    
    	I have a customer running ALL-IN-1 V3.2 with X.500.
    
    	They have many surnames that include the character "/"in the middle
    of it, as for example:
    
    	   S=Marcia/Dep1
    
    	When they insert the user from ALL-IN-1 , they use "//" when the "/"
needs to appear in the middle of a field as the surname for example.
    
    	The problem is that DXIM permits that the user inserts a surname
    using just one  "/". They have many users in this situation but when
    they need to update these users from inside ALL-IN-1, it generates an
    error because the surname has just one "/" in the middle of it. The
    customer is updating another field. 
    
    	Do they have to change all the users inserted from DXIM with just
    one slash in the surname or is there anothe way to make ALL-IN-1 work
    with these surnames?
    
    	Thanks .. Marcia
T.RTitleUserPersonal
Name		DateLines
2693.1IOSG::CARLINDick Carlin IOSG, Reading, EnglandThu May 22 1997 17:056
    Marcia
    
    Why are you doubling the / for ALL-IN-1? That is only necessary in a
    Distinguished Name.
    
    Dick
2693.2Log from the edit DJOV09::ABREUFri May 23 1997 00:12107
Hi Dick,
    
    The customer is using the options MGT MUA E to edit an account and in
    the log shown below ,  you can see that the distinguished name uses the CN
    that is Given name + Surname and then the problem happens.
    
    	The message shown when I try to edit the account is :

Message Returned: X500 entry management job completed with errors.
    
         Marcia
          
 OA#SM_X500_Edit_YY.log
----------------------------------------------
Submitted by MANAGER on 22-MAY-1997 14:52:20.91

Update X.500 Entry Report
-------------------------

Action       : Update X.500 entry
User         : YY01
Date         : 22-Mai-1997 02:52pm
Submitted by : MANAGER

14:52:23 - User: YY01   X.500 mapping policy: A1_ORGPERSON

Mapping X.500 attributes using X.500 mapping script,
OA$LIB_SHARE:SM$X500_MAP_A1_ORGPERSON.SCP

ERROR: invalid attribute name in leaf RDN of DN,
       /C=BR/O=PETROBRAS/CN=D Desol/Didia

The Distinguished Name generated by the X.500 mapping policy requires
that the user's X.500 entry is renamed
Old DN: /C=BR/O=PETROBRAS/CN=D Desol/Didia
New DN: /C=BR/O=Petrobras/OU=Serinf/CN=Desol//Didia

ERROR: invalid attribute name in leaf RDN of DN,
       /C=BR/O=PETROBRAS/CN=D Desol/Didia

ERROR: only the last element of the Distinguished Name can be changed

No changes made to the X.500 Directory

..........

Details of the X.500 entry (as defined by the X.500 mapping policy):

  Distinguished Name (DN):
    /C=BR/O=Petrobras/OU=Serinf/CN=Desol//Didia

  Attributes: [ 28 ]
    commonName  [ 1 value ]
      Desol/Didia
    objectClass  [ 4 values ]
      person
      organizationalPerson
      decMailUser
      mhs-user
    GivenName  [ 0 values ]
    Surname  [ 1 value ]
      Desol/Didia
    Initials  [ 0 values ]
    GenerationalQualifier  [ 0 values ]
    organizationalUnitName  [ 1 value ]
      Serinf
    organizationName  [ 1 value ]
      Petrobras
    countryName  [ 1 value ]
      BR
    dec-mts-admd-name  [ 1 value ]
      EMBRATEL.INTL
    dec-mts-prmd-name  [ 1 value ]
      PETROBRAS
    mhs-or-addresses  [ 1 value ]
      S=Desol/Didia; S=Desol/Didia; CN=Desol/Didia; CN=Desol/Didia; O=Petrobras;
 OU1=Serinf; P=PETROBRAS; A=EMBRATEL.INTL; C=BR
    decMRAddress  [ 1 value ]
      YY01@A1@C6000E
    decAltMRAddress  [ 0 values ]
    dec-mts-talk-other-CCITT-domain  [ 1 value ]
      1
    decDDSModificationTimestamp  [ 0 values ]
    telephonenumber  [ 0 values ]
    localityName  [ 1 value ]
      c6000e
    postalAddress  [ 0 values ]
    postalCode  [ 0 values ]
    preferredDeliveryMethod  [ 1 value ]
      [Attribute value is a list]
        1
        0
    Title  [ 0 values ]
    decALL-IN-1UserName  [ 1 value - defined by ALL-IN-1 ]
      YY01
    decALL-IN-1UAName  [ 1 value - defined by ALL-IN-1 ]
      /C=BR/O=PETROBRAS/CN=ALL-IN-1 C6000E
    decMailDestination  [ 1 value - defined by ALL-IN-1 ]
      /C=BR/O=PETROBRAS/CN=ALL-IN-1 C6000E
    decMailNonDeliver  [ 0 values - defined by ALL-IN-1 ]
    decX400Redirect  [ 0 values - defined by ALL-IN-1 ]
    decPreferredMailAddress  [ 1 value - defined by ALL-IN-1 ]
      mhs-or-addresses

14:52:28 - User: YY01 completed with errors

=============================================================
2693.3IOSG::CARLINDick Carlin IOSG, Reading, EnglandFri May 23 1997 15:4220
    
    Marcia
    
    Yes, sorry, I forgot that the surname end up in the cn and therefore in
    the DN.
    
    And, blush, blush, the routine that produces the readable DN from the
    internal encoding (when we have found the original entry) is failing to
    double up the / character. Could you report the problem formally,
    meanwhile we'll try and think of a way to fix it by changing the
    mapping policy script.
    
    The reason for the other error you are getting is that you are
    effectively trying to move the entry down a level. Perhaps you have
    recently populated the OU field in profile entries, this would cause
    the mapping policy to include it as an extra DN term. I think you will
    have to delete and recreate entries if this is the case.
    
    Dick
2693.4Script customisation work-around?IOSG::WRENIFri May 23 1997 16:10107
Marcia,

    In the meantime you could try the following customisation change to
    OA$DO:SM_X500_DI_TOOLS.SCP which might get you round the X500$ dataset bug.

    Note that I haven't tested the change, or even ensured that the syntax is
    valid. It's a possible work-around.

    In short this is _not_ an official fix. 

    More blushes, I've also noticed a bug in the released version of the
    script that you should also mention in your bug report. The official
    script wouldn't handle RDN's with more than one doubled set of slashes.
    
    In the customisation details below the change from.....
    
       	   GET #ndr = #token "/"
    
    to.....
    
       	   GET #ndr = #ndr #token "/" 
    
    in the section..... 
    
       	   !+
       	   ! an escaped RDN delimiter, keep gobbling
       	   ! ( and un-escape the delimiter )
       	   !-
    
    fixes that bug. (ready for when the X500$ dataset is fixed)
    
    
 ==============================================================================

OA$DO:SM_X500_DI_TOOLS.SCP

In the SUBROUTINE smxd_get_superior_dn make the following change....

----
Old:

     .WHILE ( #smxd_superior_dn EQS "" ) AND ( #aboutface NES "" )
        !
        GET_TOKEN #aboutface,#token,"/"
        !
        .IF #aboutface:1 NES "/"
        .THEN
           !+
           ! No escaped RDN delimiters, so exit the loop
           !-
           GET #ndr = #ndr #token
           GET #smxd_superior_dn = #aboutface::H
        .ELSE
           !+
           ! an escaped RDN delimiter, keep gobbling
           ! ( and un-escape the delimiter )
           !-
           GET #ndr = #token "/"
           GET_TOKEN #aboutface,#token,"/"
        .END_IF
     .END_WHILE

----
New:

     .WHILE ( #smxd_superior_dn EQS "" ) AND ( #aboutface NES "" )
        !
        GET_TOKEN #aboutface,#token,"/"
        !
        .IF #aboutface:1 NES "/"
        .THEN
	   !+
	   ! TEMP: Customisation to tolerate X500$ bug that means that
	   !       / characters within RDN attribute values are not being
	   !       doubled as expected in DN input to X500$
	   !-
	   .IF ( FN$LOCATE( #token, "=" ) EQ 0 )
	   .THEN
	      !+
	      ! Continue looking if there isn't an = character in the
	      ! string following the / character. We have a non-doubled
	      ! slash in the attribute value. Retain the / character in the
	      ! value
	      !-
	      GET #ndr = #ndr #token "/"
	   .ELSE
		!+
		! No escaped RDN delimiters, so exit the loop
		!-
		GET #ndr = #ndr #token
		GET #smxd_superior_dn = #aboutface::H
           .END_IF
	   !+
	   ! TEMP: Customisation end
	   !-
        .ELSE
           !+
           ! an escaped RDN delimiter, keep gobbling
           ! ( and un-escape the delimiter )
           !-
           GET #ndr = #ndr #token "/"
           GET_TOKEN #aboutface,#token,"/"
        .END_IF
     .END_WHILE

----
2693.5OKDJOV09::ABREUFri May 23 1997 18:256
    Hi,
    
    	I'll open a formal call and I'll try the workaround to see if it
    works ... 
    
    Thanks .. Marcia
2693.6no more //DJOV09::ABREUFri May 23 1997 22:386
    Hi,
    
    This workaround will solvethe problem of having to use two slashs in
    the surname. 
    
    Marcia
2693.7exDJOV09::ABREUTue Jun 03 1997 16:465
    Hi,
    
    The workaround didn't work. I will open a formal call today.
    
    	hanks .. Marcia