简体繁体 English

将 Groupwise/Novell 帐户与 java 应用程序同步

[英]Syncing Groupwise/ Novell accounts with a java application

原文 2011-05-31 19:02:53 3 1 java/ login/ novell/ groupwise

I have a Java application which has it's own table of username's and passwords.我有一个 Java 应用程序，它有自己的用户名和密码表。 We are trying to upgrade the system so that a user may simply use their groupwise/novell accounts to login, essentially, syncing their accounts.我们正在尝试升级系统，以便用户可以简单地使用他们的 groupwise/novell 帐户登录，本质上是同步他们的帐户。

What would be required to authenticate their username and pw?验证他们的用户名和密码需要什么？ I know how to retrieve emails using pop3/imap from groupwise in java, so i can try to login that way and make sure I get a successful login, but i'm sure there is a better way.我知道如何使用 pop3/imap 从 java 中的 groupwise 检索电子邮件，所以我可以尝试以这种方式登录并确保我成功登录，但我确信有更好的方法。

1 个解决方案

It will depend.这将取决于。 GroupWise has two different password approaches. GroupWise 有两种不同的密码方法。

User a distinct GW password, stored in the GW databases用户使用不同的 GW 密码，存储在 GW 数据库中
User an LDAP password, usually pointed against eDirectory使用 LDAP 密码，通常指向 eDirectory

If the first case, I am not sure how you might do it, though I suppose a POP connect in Java testing for success would work.如果是第一种情况，我不确定你会怎么做，尽管我认为 Java 中的 POP 连接测试是否成功。

If the second case, then you would just need to know the eDirectory LDAP server information, and connect to that.如果是第二种情况，那么您只需要知道 eDirectory LDAP 服务器信息并连接到该信息即可。 Get the server, whether it requires SSL/TLS or not, an account with sufficient rights to find users in eDirectory, and then decide what attribute you will use to find users.获取服务器（无论它是否需要 SSL/TLS）、具有足够权限的帐户以在 eDirectory 中查找用户，然后决定您将使用什么属性来查找用户。 Probably uniqueID in eDirectory (uid via LDAP) but you will need to ask if it is populated in this system.可能是 eDirectory 中的唯一 ID（通过 LDAP 的 uid），但您需要询问它是否已在此系统中填充。 Due to historical vagaries of eDirectory, early tools did not always set uniqueID on users.由于 eDirectory 的历史变幻莫测，早期的工具并不总是为用户设置 uniqueID。 Thus it is possible not every object has it set.因此，并非每个 object 都设置了它。 However, all modern tools set it, so it would only be a one time fix.但是，所有现代工具都设置了它，因此它只是一次修复。 CN is a bad choice as it can be multi valued. CN 是一个糟糕的选择，因为它可以是多值的。 Of course, if email address are populated, you could require mail (Internet EMail Address in eDirectory).当然，如果 email 地址已填充，您可能需要邮件（eDirectory 中的 Internet EMail 地址）。

Basically how you would do any standard LDAP integration.基本上你将如何做任何标准的 LDAP 集成。 There are libraries like LDAPChai to make this easier as well.像 LDAPChai 这样的库也可以使这更容易。