Anonymous_User Absent Member.
Absent Member.
299 views

Uid Missing


Hello,

We're implementing a wireless network at one of our schools. Joining a
particular wireless ssid produces a captive portal. To authenticate,
the user has to supply their edirectory username/password. Some users
worked, some didn't. Turns out I have a bunch of older user accounts
that don't have the uid attribute filled in. I'm guessing some past
iteration edirectory didn't have that attribute in the schema. Newer
accounts have the uid attribute filled.

We can add it using console one by going to the other tab and adding the
uid. Is there any downside or potential problems by manually filling in
the attribute?

Thanks in advance.

-Ian


--
imc
------------------------------------------------------------------------
imc's Profile: https://forums.netiq.com/member.php?userid=1653
View this thread: https://forums.netiq.com/showthread.php?t=46302

Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Uid Missing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The UID attribute has been auto-created to match the CN value since
ConsoleOne shipped... however long ago that was. nwadmin did NOT do it,
so your users are probably as old as nwadmin; also, if you created users
outside of ConsoleOne/iManager (such as via LDAP) your own manual
creations may have omitted the attribute.

Downsides? No... probably all upsides. Generally speaking I'd
recommend making sure the values are all lower-case since most things
which use them (like LUM, or RADIUS, etc.) will want users in
lower-case, though some systems now ignore case because of user training
issues there (LUM/namcd can ignore case now, for example).

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJQuSGxAAoJEF+XTK08PnB5dAYP/1hV+0IsE1uUNYZT6Rowytdx
R5FRUI4fCkTKu5NgEbn1U5bfU0ebQQaHQutnhfxO2tjg7Y1CU4baeOHgKWbfwiK7
6BymUW5KBNeUiXS9ot+QozclC2Pjt+7lgR4VKjJwlpu6kD7GfmRzYUsXGPC6iYr0
NuTmYNSgdFri3+9pbpixgmm2ZCPgOZBdrmUt7UVpQF5NPBemN1aFFouJo8JlwC+V
B/4yiWimqIO4OrdabW1ALrzvdIOueHiyp2tDWNKe3ROSItHcRu8s2/bYJN/bNr/f
h1KJWrf3kESZ+kMUeRR7Q1kuVyJv3+f8GF39kF9B3feGYAt+ab1YZp0yie+25rWo
dCWYZ4fUeBBtLe2dotGRicbSvqPm4fb1nwShDWi4h056H7CFAQdzZDORKF4GH32D
us3q8MQG5VAVJ/1Lhn772pfS6aSDVC/CUenuUCDZSvKOxzfBPmzFIBbpSjmzCfkd
OnXDfRc0ih0VqJ8RvC9jsEJYBXzs8/XPMvoapI+v3XLh/2cj2lRHNimWbhWO0rhy
jnG5D/AfzfzVHImCdnqvEn1S7Tc4qOUGjRtbFJxE32c2E5mCy8vbRg5ZlXh9pwao
uuAgw0FM6iSOYT3XtCwTZEgF95VesrKASpu7FBZEsn+fU1G3SFp7gzh2sh+wQ0I0
Bg0Ubghz7jwllAerlEgd
=JIKT
-----END PGP SIGNATURE-----
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.