You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Thibault Le Meur (Created) (JIRA)" <ji...@apache.org> on 2012/03/30 16:28:28 UTC
[jira] [Created] (OPENMEETINGS-113) Define a default Login-Domain
(ie an Ldap domain) to be automatically selected in the frontend login
window
Define a default Login-Domain (ie an Ldap domain) to be automatically selected in the frontend login window
-----------------------------------------------------------------------------------------------------------
Key: OPENMEETINGS-113
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
Project: Openmeetings
Issue Type: Improvement
Affects Versions: 2.0 Apache Incubator Release
Environment: N/A
Reporter: Thibault Le Meur
Priority: Minor
When an administrator defines an LDAP "domain", his users are likely to authenticate against it and not against the default "Internal DB" that is automatically selected in the login window.
This is not an issue for users already defined as LDAP users in the internal DB because OM is able to read the LDAP domain from teh DB in order to perfform authentication.
However this is an issue for the first login because most users would forget to set the Domain and thus would fail to login for the first time (resulting in multiple calls to the It service... and I would definitely like to avoid this situation ;-) .
I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-113) Define a default Login-Domain
(ie an Ldap domain) to be automatically selected in the frontend login
window
Posted by "Thibault Le Meur (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thibault Le Meur updated OPENMEETINGS-113:
------------------------------------------
Attachment: ldap_default_id.diff
Proposed patch that implements new configuration parameter ldap_default_id:
* ImportInitvalues.java: auto create the parameter with default to 0 (previous behaviour)
* MainService.java: returns ldap_default_id as fifth value in getLoginOptions
* WebContent/src/base/auth/checkLoginData.lzx: set the Ldap domain
> Define a default Login-Domain (ie an Ldap domain) to be automatically selected in the frontend login window
> -----------------------------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-113
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
> Project: Openmeetings
> Issue Type: Improvement
> Affects Versions: 2.0 Apache Incubator Release
> Environment: N/A
> Reporter: Thibault Le Meur
> Priority: Minor
> Labels: ldap, loginmodule
> Attachments: ldap_default_id.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When an administrator defines an LDAP "domain", his users are likely to authenticate against it and not against the default "Internal DB" that is automatically selected in the login window.
> This is not an issue for users already defined as LDAP users in the internal DB because OM is able to read the LDAP domain from teh DB in order to perfform authentication.
> However this is an issue for the first login because most users would forget to set the Domain and thus would fail to login for the first time (resulting in multiple calls to the It service... and I would definitely like to avoid this situation ;-) .
> I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-113) Define a default Login-Domain
(ie an Ldap domain) to be automatically selected in the frontend login
window
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-113.
-----------------------------------------
Assignee: Maxim Solodovnik
Closing all old 'Resolved' issues
> Define a default Login-Domain (ie an Ldap domain) to be automatically selected in the frontend login window
> -----------------------------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-113
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
> Project: Openmeetings
> Issue Type: Improvement
> Affects Versions: 2.0 Apache Incubator Release
> Environment: N/A
> Reporter: Thibault Le Meur
> Assignee: Maxim Solodovnik
> Priority: Minor
> Labels: ldap, loginmodule
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: ldap_default_id.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When an administrator defines an LDAP "domain", his users are likely to authenticate against it and not against the default "Internal DB" that is automatically selected in the login window.
> This is not an issue for users already defined as LDAP users in the internal DB because OM is able to read the LDAP domain from teh DB in order to perfform authentication.
> However this is an issue for the first login because most users would forget to set the Domain and thus would fail to login for the first time (resulting in multiple calls to the It service... and I would definitely like to avoid this situation ;-) .
> I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-113) Define a default Login-Domain
(ie an Ldap domain) to be automatically selected in the frontend login
window
Posted by "SebastianWagner (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner resolved OPENMEETINGS-113.
------------------------------------------
Resolution: Fixed
I've commited to trunk. Thanks for the path Thibault!
Just a minor change: You need to be carefully with the order of the calls, if the RemoteCall to get the numbre of available configs is slower then the RPC call to get the config set, then your implementation would not work. That is why I added:
"parent.parent.getLoginOptions.doCall();"
into getActiveLdapConfigs and removed the "doCall()" in the oninit handler of getLoginOptions.
> Define a default Login-Domain (ie an Ldap domain) to be automatically selected in the frontend login window
> -----------------------------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-113
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
> Project: Openmeetings
> Issue Type: Improvement
> Affects Versions: 2.0 Apache Incubator Release
> Environment: N/A
> Reporter: Thibault Le Meur
> Priority: Minor
> Labels: ldap, loginmodule
> Attachments: ldap_default_id.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When an administrator defines an LDAP "domain", his users are likely to authenticate against it and not against the default "Internal DB" that is automatically selected in the login window.
> This is not an issue for users already defined as LDAP users in the internal DB because OM is able to read the LDAP domain from teh DB in order to perfform authentication.
> However this is an issue for the first login because most users would forget to set the Domain and thus would fail to login for the first time (resulting in multiple calls to the It service... and I would definitely like to avoid this situation ;-) .
> I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENMEETINGS-113) Define a default Login-Domain
(ie an Ldap domain) to be automatically selected in the frontend login
window
Posted by "SebastianWagner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner updated OPENMEETINGS-113:
-----------------------------------------
Fix Version/s: 2.0 Apache Incubator Release
> Define a default Login-Domain (ie an Ldap domain) to be automatically selected in the frontend login window
> -----------------------------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-113
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-113
> Project: Openmeetings
> Issue Type: Improvement
> Affects Versions: 2.0 Apache Incubator Release
> Environment: N/A
> Reporter: Thibault Le Meur
> Priority: Minor
> Labels: ldap, loginmodule
> Fix For: 2.0 Apache Incubator Release
>
> Attachments: ldap_default_id.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When an administrator defines an LDAP "domain", his users are likely to authenticate against it and not against the default "Internal DB" that is automatically selected in the login window.
> This is not an issue for users already defined as LDAP users in the internal DB because OM is able to read the LDAP domain from teh DB in order to perfform authentication.
> However this is an issue for the first login because most users would forget to set the Domain and thus would fail to login for the first time (resulting in multiple calls to the It service... and I would definitely like to avoid this situation ;-) .
> I'm preparing a patch for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira