manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Using a password authority to supply repository connector password
Date Thu, 12 May 2016 21:17:30 GMT
I really can't advise you on this, since you would be writing your
extension connector by overriding non-public methods etc.  Anything you
write could not be guaranteed to continue to work for subsequent releases
unless you forked the specific connectors entirely.

Thanks,
Karl


On Thu, May 12, 2016 at 2:51 PM, <ashutosh.rai@wipro.com> wrote:

> Hi Karl,
>
>
>
> Thank you for your reply.
>
>
>
> It would be great to have this as a supplemental functionality in future,
> and if and when available, we would use it.
>
>
>
> However, we need something near term and I am thinking of extending the
> connectors we want to use to enable this. I.e., create a custom class
> extending the framework provided SharePoint connector and override the
> necessary methods to plug the password obtained from the password authority
> (currently I see that I need to override the connect method in the
> SharePoint repository connector class for a quick and dirty
> implementation).
>
>
>
> Please let me know if the approach makes sense. Would appreciate any
> suggestions to implement it in a clean way.
>
>
>
> When the feature becomes available as part of the framework, we will
> switch over to the framework connector.
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
>
>
>
>
>
> *From: *Karl Wright <daddywri@gmail.com>
> *Sent: *12 May 2016 19:13
> *To: *user@manifoldcf.apache.org
> *Subject: *Re: Using a password authority to supply repository connector
> password
>
>
>
> Hi Ashutosh,
>
>
>
> Access to the UI or API can currently be abstracted through an interface,
> but nobody has attempted to do this for individual connector
> authentication.  There is no current infrastructure available to support
> this either.  Indeed, supporting this functionality would require:
>
>
>
> (1) changes to all the connection configuration UIs that would support
> this functionality
>
> (2) infrastructure to allow a custom interface implementation to be
> invoked whenever connection needs to occur for an authenticated connection
>
> (3) a means of specifying (e.g. registering) the class name of the
> implementation to instantiate
>
>
>
> This is, as you point out, not very easy to do, and will take a
> substantial amount of work to address.  If you are willing to wait for some
> months we might be able to address it.
>
>
>
> Karl
>
>
>
>
>
>
>
> On Thu, May 12, 2016 at 1:56 PM, <ashutosh.rai@wipro.com> wrote:
>
> Hello,
>
>
>
> Firstly, thank you for the time and effort in building and maintaining the
> Apache Manifoldcf framework.
>
>
>
> We are evaluating it for a requirement and would like to plug in a custom
> password authority for repository password with the SharePoint repository
> connector and the windows share repository connector.
>
>
>
> Instead of specifying the repository password on the UI, we would like the
> connector to call a Java API to looks up for password against a password
> authority using a key (typically a server and user name combination).
>
>
>
> After going through the Apache Manifold documentation and the source code,
> it appears that this may not be straightforward.
>
>
>
> We would appreciate any guidance on how to implement this either via
> configuration and/or via code modifications.
>
>
>
> Thank you.
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
>
>
>
>
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>

Mime
View raw message