[jira] [Commented] (CONNECTORS-1752) Solr 9 Ingester connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807237#comment-17807237 ] Guylaine Bassette commented on CONNECTORS-1752: --- I have created the [CONNECTOR-1752|https://github.com/guylaine-bassette/manifoldcf/tree/CONNECTORS-1752] in my Fork Project. The solution is ready to merge as soon as my [PR 160 - Fix URLs for manifoldCF plugins downloads for make-core-deps|https://github.com/apache/manifoldcf/pull/160] is applied. > Solr 9 Ingester connector > - > > Key: CONNECTORS-1752 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1752 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.26 >Reporter: Guylaine Bassette >Priority: Major > > The current Solr ingester connector fails to ingest Sorl 9 documents properly. > The current version of the ingester uses Sorlj 9, so it probably only needs a > few adjustments to get it working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1752) Solr 9 Ingester connector
Guylaine Bassette created CONNECTORS-1752: - Summary: Solr 9 Ingester connector Key: CONNECTORS-1752 URL: https://issues.apache.org/jira/browse/CONNECTORS-1752 Project: ManifoldCF Issue Type: Improvement Components: Lucene/SOLR connector Affects Versions: ManifoldCF 2.26 Reporter: Guylaine Bassette The current Solr ingester connector fails to ingest Sorl 9 documents properly. The current version of the ingester uses Sorlj 9, so it probably only needs a few adjustments to get it working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785779#comment-17785779
]
Guylaine Bassette commented on CONNECTORS-1749:
---
Hello,
I have added a few more details in the description to help.
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-28-57-668.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> you need to have a working query for the group part. Indeed, if the groups
> query is invalid and if you obtain an error code 52 into ldapsearch and MCF
> logs, it means that this query is the issue.
> Try the default query of MCF :
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-28-57-668.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But you
need to have a working query for the group part. Indeed, if the groups query is
invalid and if you obtain an error code 52 into ldapsearch and MCF logs, it
means that this query is the issue.
Try the default query of MCF :
{{}}
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: (was: image-2023-11-14-08-12-53-191.png)
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
>
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-27-49-930.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Description:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
h2. Debug, help for configuration
Regarding the LDAP Authority configuration:
!image-2023-11-14-08-27-49-930.png!
When you have completed the first part in green, it is equivalent to this
command line with the tool ldapsearch:
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
"uid=myuser,ou=People,dc=francelabs,dc=com" -b "ou=people,dc=francelabs,dc=com"
"(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
Even if you get the expected result with this query, you might think that it is
not important to fill in the red part concerning the group attributes. But when
you try to
If this part is OK, you need to have a working query for the group part.
Indeed, if the groups query is invalid and if you obtain an error code 52 into
ldapsearch and MCF logs, it means that this query is the issue.
Try the default query of MCF :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
If you obtain an error code 52 and even if you are not interested by retrieving
the groups, you MUST have a query that works. So change the query until the
error code disappears.
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
"(&(objectClass=groupOfNames))"}}
You will obtain some objects. Choose one with the OU that you want and enter
this OU into MCF configuration. Example :
{{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
"ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
was:
The group parameters are mandatory in MCF, but some LDAP servers don't require
such parameters to answer to queries related to a user in order to get back
authorization tokens. With such LDAP servers, you therefore do not need to
input group related information to have a working search.
But there is a negative aspect: there are scenarios where you may NOT know any
group related information since it is not needed for those LDAP servers. But
since MCF requires these parameters, anything that you put in, in order for MCF
to validate the configuration, will be sent to the LDAP server that will
generate an error answer because the group parameters are incorrect: Error code
52 - Object Not Found Error.
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-27-49-930.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: image-2023-11-14-08-28-57-668.png
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
>
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[
https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guylaine Bassette updated CONNECTORS-1749:
--
Attachment: (was: image-2023-11-14-08-27-49-930.png)
> LDAP Authority: make Group parameters optional
> --
>
> Key: CONNECTORS-1749
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1749
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LDAP authority
>Reporter: Guylaine Bassette
>Priority: Minor
> Attachments: image-2023-11-14-08-28-57-668.png
>
>
> The group parameters are mandatory in MCF, but some LDAP servers don't
> require such parameters to answer to queries related to a user in order to
> get back authorization tokens. With such LDAP servers, you therefore do not
> need to input group related information to have a working search.
>
> But there is a negative aspect: there are scenarios where you may NOT know
> any group related information since it is not needed for those LDAP servers.
> But since MCF requires these parameters, anything that you put in, in order
> for MCF to validate the configuration, will be sent to the LDAP server that
> will generate an error answer because the group parameters are incorrect:
> Error code 52 - Object Not Found Error.
> h2. Debug, help for configuration
> Regarding the LDAP Authority configuration:
> !image-2023-11-14-08-27-49-930.png!
> When you have completed the first part in green, it is equivalent to this
> command line with the tool ldapsearch:
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -D
> "uid=myuser,ou=People,dc=francelabs,dc=com" -b
> "ou=people,dc=francelabs,dc=com"
> "(&(objectClass=inetOrgPerson)(uid=any_user_uid))"}}
> Even if you get the expected result with this query, you might think that it
> is not important to fill in the red part concerning the group attributes. But
> when you try to
> If this part is OK, you need to have a working query for the group part.
> Indeed, if the groups query is invalid and if you obtain an error code 52
> into ldapsearch and MCF logs, it means that this query is the issue.
> Try the default query of MCF :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=groups,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
> If you obtain an error code 52 and even if you are not interested by
> retrieving the groups, you MUST have a query that works. So change the query
> until the error code disappears.
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b "dc=francelabs,dc=com"
> "(&(objectClass=groupOfNames))"}}
> You will obtain some objects. Choose one with the OU that you want and enter
> this OU into MCF configuration. Example :
>
> {{ldapsearch -x -H ldap://ldap.francelabs.com:389 -b
> "ou=system,dc=francelabs,dc=com" "(&(objectClass=groupOfNames))"}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-27-49-930.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png, > image-2023-11-14-08-27-49-930.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-21-20-901.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: (was: image-2023-11-14-08-21-20-901.png) > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Attachment: image-2023-11-14-08-12-53-191.png > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > Attachments: image-2023-11-14-08-12-53-191.png > > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
[ https://issues.apache.org/jira/browse/CONNECTORS-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guylaine Bassette updated CONNECTORS-1749: -- Description: The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Error code 52 - Object Not Found Error. was: The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Object Not Found Error. > LDAP Authority: make Group parameters optional > -- > > Key: CONNECTORS-1749 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 > Project: ManifoldCF > Issue Type: Improvement > Components: LDAP authority >Reporter: Guylaine Bassette >Priority: Minor > > The group parameters are mandatory in MCF, but some LDAP servers don't > require such parameters to answer to queries related to a user in order to > get back authorization tokens. With such LDAP servers, you therefore do not > need to input group related information to have a working search. > > But there is a negative aspect: there are scenarios where you may NOT know > any group related information since it is not needed for those LDAP servers. > But since MCF requires these parameters, anything that you put in, in order > for MCF to validate the configuration, will be sent to the LDAP server that > will generate an error answer because the group parameters are incorrect: > Error code 52 - Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CONNECTORS-1749) LDAP Authority: make Group parameters optional
Guylaine Bassette created CONNECTORS-1749: - Summary: LDAP Authority: make Group parameters optional Key: CONNECTORS-1749 URL: https://issues.apache.org/jira/browse/CONNECTORS-1749 Project: ManifoldCF Issue Type: Improvement Components: LDAP authority Reporter: Guylaine Bassette The group parameters are mandatory in MCF, but some LDAP servers don't require such parameters to answer to queries related to a user in order to get back authorization tokens. With such LDAP servers, you therefore do not need to input group related information to have a working search. But there is a negative aspect: there are scenarios where you may NOT know any group related information since it is not needed for those LDAP servers. But since MCF requires these parameters, anything that you put in, in order for MCF to validate the configuration, will be sent to the LDAP server that will generate an error answer because the group parameters are incorrect: Object Not Found Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773277#comment-17773277 ] Guylaine Bassette commented on CONNECTORS-1740: --- Hello [~kwri...@metacarta.com], Thanks to have merged my Zookeeper fix ! We have tested it in our application and everything works well: job configuration and Solr indexation. > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773266#comment-17773266 ] Guylaine Bassette commented on CONNECTORS-1740: --- Hello [~mingchun.zhao], Thanks for your contribution with Java 11 ! (y) I have integrated your patch with my contribution to fix the Zookeeper bug (PR 150, al ready merged to the master Branch). > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CONNECTORS-1740) Solr 9 output connector
[ https://issues.apache.org/jira/browse/CONNECTORS-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17744455#comment-17744455 ] Guylaine Bassette commented on CONNECTORS-1740: --- Hello, We have created an issue to the ZooKeeper Team : https://issues.apache.org/jira/browse/ZOOKEEPER-4722. We provided them a ManifoldCF fork project they can build to reproduce the bug (https://gitlab.datafari.com/sandboxespublic/manifoldcf). > Solr 9 output connector > --- > > Key: CONNECTORS-1740 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1740 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 2.23 >Reporter: Julien Massiera >Assignee: Julien Massiera >Priority: Major > Attachments: CONNECTORS-1740.patch > > > The current Solr output connector is not compatible with Solr 9.x > We need to update the connector with SolrJ 9 and make sure that the custom > code (multipart post requests, basic/preemptive auth) is still required, and, > in case it is, port it ! -- This message was sent by Atlassian Jira (v8.20.10#820010)
