Stefan

> Apologize, I should have written Hi Dave :)


No worries!  :-)

I get that all the time!  It is a side effect of having a last name that can 
sometimes be used as a first name.

You wrote under separate cover:

I was able to reproduce that exact same error. The reason is that for
the first prescriptiveACI the last closing curly brace is not indented.

The error returned from the server is quite verbose but the actual
invalid attribute is

   }: UNKNOWN

Do you use the Studio LDIF editor and LDIF import? That seems to be a
bug in Studio. It seems it takes the line with the closing curly bracket
and "invents" the "UNKNOWN" value. Can you please file a bug in Jira?

So simple solution it to indent it by one space, that's required by the
LDIF spec.

Yup, that was it!  Thanks, by adding a space, it imports now without error, and 
I've verified that enhanced (advanced?) security is now working as expected.

Actually, I didn't use the Studio LDIF editor, I simply copy-n-pasted from the 
web page into a plain text file and did a File => Import within Studio.

Personal note: I hate languages where whitespace is significant, which is why I 
still use PERL over Python.  So I had no idea what ' }: UNKNOWN' was compelling 
about, because all of the curly braces were matched, and I don't normally think 
about whitespace being important (being a Java / PERL programmer, and working 
with XML / JSON).

Finally, you wrote under separate cover (regarding my question about root vs. 
non-root):

Do you use the tar.gz or zip archive? That works, I just unzipped it (as
my normal user so all files are owned by me) and started it.

For the bin/deb/rpm packages installers I don't know.

Actually, I used the binary package, because I was installing ApacheDS on a 
Raspberry Pi.  Since that is an ARM architecture (and not x86_64), I had to use 
the binary (thankfully, Java's "write once / run anywhere" tag line actually 
works!).

I am tabling this for now, since after thinking about it, there must have been 
something that kicked off the Linux systemd .service file while I was in the 
middle of changing file ownerships / permissions, since the JVM knows nothing 
about root and is not installed with root priviliges (unlike some programs that 
are -- e.g., Apache web server, which starts as root and then switches to 
another user).  So I'm assuming this was cockpit error on my part.

Nonetheless, thanks for all your help.

Regards,

Dave.

> On Apr 7, 2021, at 3:31 PM, Stefan Seelmann <[email protected]> wrote:
> 
> On 4/7/21 9:28 PM, Stefan Seelmann wrote:
>> Hi Filip,
> Apologize, I should have written Hi Dave :)
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

Reply via email to