[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028090#comment-13028090 ] Karl Wright commented on CONNECTORS-195: The patch requires the name of an attribute that all users have. uid is what it uses now. Online references are not clear on whether or not this will always work with Active Directory. It especially does not seem to exist for Windows 2000. Another suggestion is sAMAccountName, which exists for all versions of Windows. Replacing uid in the patch with sAMAccountName may therefore make it work better. Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028091#comment-13028091 ] Karl Wright commented on CONNECTORS-195: The following reference is very helpful. http://msdn.microsoft.com/en-us/library/ms679635%28v=VS.85%29.aspx Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-174) The standard logging.ini file for the Quick Start should set a log format that includes at least date and time
[ https://issues.apache.org/jira/browse/CONNECTORS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028217#comment-13028217 ] Erlend Garåsen commented on CONNECTORS-174: --- I suggest something like this: WARN 2011-05-03 15:19:19,145 (Thread-326) - Error communicating with Ingestion API: Connection refused java.net.ConnectException: Connection refused The standard logging.ini file for the Quick Start should set a log format that includes at least date and time -- Key: CONNECTORS-174 URL: https://issues.apache.org/jira/browse/CONNECTORS-174 Project: ManifoldCF Issue Type: Improvement Components: Examples Affects Versions: ManifoldCF next Reporter: Karl Wright Priority: Minor The log format as currently set by default for the Quick Start could be better if it included a date, time, and maybe a thread ID. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028276#comment-13028276 ] Erlend Garåsen commented on CONNECTORS-194: --- I suggest that the path to the Javadoc root is changed from http://incubator.apache.org/connectors/javadoc.html to http://incubator.apache.org/connectors/api/ (index.html) Then it is much more easier to exclude those docs by creating rules in a cli.xconf file, for example: exclude pattern=api/**/ Take a look at the following part in the Forrest's faq: http://forrest.apache.org/docs_0_80/faq.html#cli-xconf Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright commented on CONNECTORS-194: cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us) because not all connectors are buildable or can be javadoc'd, depending on the existence of the needed third-party libraries. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CONNECTORS-194) Forrest doc build always gets an error because of relative references to javadoc roots
[ https://issues.apache.org/jira/browse/CONNECTORS-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028282#comment-13028282 ] Karl Wright edited comment on CONNECTORS-194 at 5/3/11 4:08 PM: cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us). Moving javadoc.html to api/index.html for this purpose is also OK if we can get forrest to work with it properly in that location. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. was (Author: kwri...@metacarta.com): cli-xconf seems definitely the way to go. But we're still going to need a jumping-off page that is handled by Forrest (which is what javadoc.html does for us) because not all connectors are buildable or can be javadoc'd, depending on the existence of the needed third-party libraries. If the api subdirectory is the new place where the javadoc roots are all put, that's fine by me. Forrest doc build always gets an error because of relative references to javadoc roots -- Key: CONNECTORS-194 URL: https://issues.apache.org/jira/browse/CONNECTORS-194 Project: ManifoldCF Issue Type: Improvement Components: Documentation Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Forrest is not very happy with generating a relative link to the javadoc roots, since the javadoc itself is not under Forrest's control. Somebody needs to find a better way of handling this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reassigned CONNECTORS-195: -- Assignee: Karl Wright Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CONNECTORS-195) Active directory authority doesn't handle unknown user case properly
[ https://issues.apache.org/jira/browse/CONNECTORS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-195. Resolution: Fixed Fix Version/s: ManifoldCF next Verified that the committed fix does the expected thing on a certain user's setup. Awaiting final verification that it does not break a user with a correct setup, although this would be extremely unlikely. Active directory authority doesn't handle unknown user case properly Key: CONNECTORS-195 URL: https://issues.apache.org/jira/browse/CONNECTORS-195 Project: ManifoldCF Issue Type: Bug Components: Active Directory authority Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF next Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF next Attachments: CONNECTORS-195.patch The active directory authority does not properly detect an non-existing user in Active Directory. Instead it returns S-1-1-0, which permits the unknown user to see all public documents. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
