Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@manifoldcf.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for dev@manifoldcf.apache.org)
MIME-Version: 1.0
In-Reply-To: 
 <CAB-fSbxmxegVa=umjYYJ67UNMvuUyz0zXPKL=pLAuFPpGPaQqA@mail.gmail.com>
References: 
 <CAB-fSbwbE+d45tcO0RU5J58y4Y8BOV1-VhUB8MpKp14+0eVg=A@mail.gmail.com>
	<CALUFAGDs9mB0c5Ur-ci+1NXMjy4ZNHL91QgQ9KXH7wSs6Kg1_w@mail.gmail.com>
	<CAB-fSbxxrRD-dZ8MiFHBX_Ep7Sx52E-6-H=6hbb81-GUFQFPvQ@mail.gmail.com>
	<CALUFAGCtLy0p3=YTYaU8T_VzqwKkzoaP65CnwbKXsFWn2RYAww@mail.gmail.com>
	<CAB-fSbwc3JLcY-rfsRTcJ9Fs0d1wiKzjRnxZBaqbR=xNLDAi4w@mail.gmail.com>
	<CALUFAGCV+NbDA9mK8aPFRx3y+15v=GxS2FVTt6hZAgsMuUzS5Q@mail.gmail.com>
	<CAB-fSbwK_6+shU1vvFrHwrW9Qu4nFam5nESEw2E6RxQ=d2C8HA@mail.gmail.com>
	<CAB-fSbybrFZdgVqPh-CxOM5YV_Gsb5P_EDVd=W8jH2DjWdQFNg@mail.gmail.com>
	<CALUFAGA7N7JFQwk4M3=uG3bcr5+kHCw+xmyLgm11KjdQ=faboQ@mail.gmail.com>
	<CAB-fSbxmxegVa=umjYYJ67UNMvuUyz0zXPKL=pLAuFPpGPaQqA@mail.gmail.com>
Date: Tue, 21 Apr 2015 12:47:45 -0400
Message-ID: 
 <CALUFAGBQtU-o9mkh1-OkoJZU82VZfyChMCdsO-5kKQGCxKtT8Q@mail.gmail.com>
Subject: Re: [Repository Connector] In Job Repository Config modification
From: Karl Wright <daddywri@gmail.com>
To: dev <dev@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=089e0102f25a4bd06c05143ece48

--089e0102f25a4bd06c05143ece48
Content-Type: text/plain; charset=UTF-8

Hi Alessandro,

In order to implement a working solution, because you cannot guarantee that
the access and refresh token might expire, you really need a separate
process that is always running to keep these current.  That is the only way
to keep Box happy without putting ridiculous constraints on ManifoldCF.
But it has its own difficulties because you need to build a lot of stuff,
and also you need to have the user handy to obtain a new access token
whenever the refresh token runs out.

Karl


On Tue, Apr 21, 2015 at 11:34 AM, Alessandro Benedetti <
benedetti.alex85@gmail.com> wrote:

> Hi Karl,
> only to discuss it again ;
> Assuming we don't want to store the username and password in ManifoldCF
> Repo Connector /Auth connector configuration.
>
> The scenario will be like this :
> 1) the first time, in an external application , the user make the login,
> get auth code, and get the first couple of access/refresh token ( what we
> automated in our previous implementation we agreed)
> 2) at this point he wants to create the Repository Connector giving in
> input :
> client_id
> client_secret
> access_token
> refresh_token.
>
> we want to be safe that every time a job starts and every time we stop and
> restart Manifold the connector is going to work.
>
> This means we need to keep updated the access/refresh token couple at each
> refresh, and be thread safe in the high concurrent/cached manifoldCF world.
>
> In your opinion, doing this, will be feasible ?
> Will be something really hard and long to achieve ?
> What is your genuine opinion ?
> Sorry if we moved back to the very beginning of this topic, just wondering
> alternate solutions to the way we approached oauth2 in box.
>
> Cheers
>
>
> 2015-04-20 12:34 GMT+01:00 Karl Wright <daddywri@gmail.com>:
>
> > Good to know.
> >
> > The Box people are certainly not using best practices where OAuth2 is
> > concerned.  And using capcha to make it even worse is pretty bad.
> >
> > Karl
> >
> >
> > On Mon, Apr 20, 2015 at 7:18 AM, Alessandro Benedetti <
> > benedetti.alex85@gmail.com> wrote:
> >
> > > P.S. sorry to answer you so late, but super busy recently and I had no
> > > chance to keep you updated
> > >
> > > 2015-04-20 12:17 GMT+01:00 Alessandro Benedetti <
> > > benedetti.alex85@gmail.com>
> > > :
> > >
> > > > Hi Karl,
> > > > thanks for your help, we succeeded in developing an automated process
> > to
> > > > get from the permanent parameters the authentication code and then
> the
> > > > access/refresh token.
> > > > Your suggestions are much appreciated.
> > > > In this way we should be compliant with Manifold standard for
> > > concurrency.
> > > > The only scenario that is really annoying is when the System
> recognise
> > > the
> > > > automated client and ask you to fill a captcha.
> > > > In that case we capture the error message and return in the
> getSession
> > > > method a message to inform the user he must authenticate manually.
> > > >
> > > > Cheers
> > > >
> > > > 2015-04-14 11:20 GMT+01:00 Karl Wright <daddywri@gmail.com>:
> > > >
> > > >> Hi Alessandro,
> > > >>
> > > >> Do not despair.  As I said before, even if all Box gives you is
> their
> > > user
> > > >> interface, we can probably use that to do the job from ManifoldCF.
> > > >>
> > > >> I am sure that the back-and-forth between the browser and their web
> > page
> > > >> is
> > > >> via HTTPS.  My first suggestion would be to install the Firefox
> plugin
> > > >> called Live Headers, which you can find here:
> > > >>
> > > >> https://addons.mozilla.org/en-us/firefox/addon/live-http-headers/
> > > >>
> > > >> You will also need the curl utility.
> > > >>
> > > >> What you want to do is obtain the contents of the web page whose
> form
> > > you
> > > >> fill in when you interact with their site.  You can get that from
> > > Firefox,
> > > >> or from curl, but you will want to understand the HTTP steps that
> you
> > go
> > > >> through to get to that page, most importantly, what cookies get set
> > and
> > > >> when.  You also want to record the HTML of the response page that
> > > includes
> > > >> the token that you will need.  If they are really badass about this
> > they
> > > >> may present it in a gif or something, and then we'd really be
> screwed,
> > > but
> > > >> if it is in normal text we should be able to do this.  You can check
> > for
> > > >> the latter situation by just viewing the result page html within the
> > > >> browser.
> > > >>
> > > >> What your goal is is to find a code way to fake out their web site
> > using
> > > >> automated means.  I would initially try constructing such a sequence
> > > >> outside of MCF by writing a small java test class that is written
> with
> > > >> httpcomponents httpclient.  I am happy to help you develop this by
> > > giving
> > > >> advice over the next couple of days.
> > > >>
> > > >> Thanks,
> > > >> Karl
> > > >>
> > > >>
> > > >>
> > > >> On Tue, Apr 14, 2015 at 5:02 AM, Alessandro Benedetti <
> > > >> benedetti.alex85@gmail.com> wrote:
> > > >>
> > > >> > I have not been working on this during tha last days, waiting for
> > some
> > > >> > feedback from Box as well, now I have an Update on this :
> > > >> >
> > > >> > "Hi Alessandro,
> > > >> >
> > > >> > There isn't a good way to bypass this process, and not something
> > that
> > > we
> > > >> > support. I'd recommend going through the browser step once, and
> just
> > > >> > maintain / renew your access/refresh tokens such that you won't
> have
> > > to
> > > >> > access a browser to make API calls.
> > > >> >
> > > >> > Apologies if this causes any inconvenience. I'll close this case
> > out,
> > > >> but
> > > >> > let me know if there's anything else I may assist with.
> > > >> >
> > > >> > Regards,
> > > >> >
> > > >> > Audrey
> > > >> > Box User Services"
> > > >> >
> > > >> > This is complicating our situation, let me try to get more
> > information
> > > >> > because this is a very bad news for our use case.
> > > >> >
> > > >> > Cheers
> > > >> >
> > > >> > 2015-04-09 13:11 GMT+01:00 Karl Wright <daddywri@gmail.com>:
> > > >> >
> > > >> > > Ok, I've looked briefly at this.
> > > >> > >
> > > >> > > I have a reference as well.  It might be good to compare and
> > > contrast:
> > > >> > >
> > > >> > >
> https://aaronparecki.com/articles/2012/07/29/1/oauth2-simplified
> > > >> > >
> > > >> > > But nevertheless, let me put down what I think the flow is:
> > > >> > >
> > > >> > > (1) You register ManifoldCF with Box and get back a client ID
> and
> > > >> client
> > > >> > > secret.  Those are permanent.
> > > >> > > (2) The next step is to get an authorization token.  This
> > currently
> > > >> seems
> > > >> > > to require interaction with a UI (at least, that's how it is
> > > >> described in
> > > >> > > the oauth documentation you provided).  The authorization token
> is
> > > >> valid
> > > >> > > for only 30 seconds.
> > > >> > > (3) From the authorization token, you can get talk to a Box API
> to
> > > >> get an
> > > >> > > access token, which gives you access to the rest of the API.
> > > >> > >
> > > >> > >
> > > >> > > Is this correct?
> > > >> > >
> > > >> > > If it is correct, then as I understand it, what we want is a
> > > >> ManifoldCF
> > > >> > > setup like this:
> > > >> > >
> > > >> > > - The connection stores: client ID, client secret, user name,
> and
> > > user
> > > >> > > password.  These are all permanent parts of the configuration.
> > > >> > > - The connector will need to be able to obtain an access token
> on
> > > >> demand,
> > > >> > > given the above information, when it concludes that it doesn't
> > have
> > > a
> > > >> > valid
> > > >> > > one already
> > > >> > > - Each connector instance will need to manage its own access
> > token.
> > > >> So
> > > >> > if
> > > >> > > there are 10 connections outstanding, there will be 10
> independent
> > > >> access
> > > >> > > tokens, each of which is obtained separately and expires
> > separately.
> > > >> > > That's the only way this connector is going to work properly
> > across
> > > >> > cluster
> > > >> > > members etc.
> > > >> > > - The process of obtaining the access token given all of the
> > > >> credentials
> > > >> > > must be completely automated as part of the connector code.
> > > >> > >
> > > >> > > Since step (2) above seems to require UI interaction, which
> would
> > > make
> > > >> > our
> > > >> > > plan not work, we should figure out whether that's in fact the
> > only
> > > >> way
> > > >> > to
> > > >> > > grant a user's permission.  My guess is that it is not; I'd put
> > much
> > > >> > money
> > > >> > > on there being a programmatic way to do this.  Even if I am
> wrong
> > > >> about
> > > >> > > that, with a little investigation of the UI interaction, I bet
> you
> > > can
> > > >> > find
> > > >> > > a URL that if you post the right information to, you will be
> able
> > to
> > > >> > figure
> > > >> > > out what you need to post to obtain the authorization token.  At
> > the
> > > >> very
> > > >> > > worst, you can use a technique similar to how the Web connector
> > > >> submits
> > > >> > > forms to fake out the Box UI.  I can certainly help you with
> that;
> > > the
> > > >> > HTML
> > > >> > > parser code is in common and is available for all connectors to
> > use.
> > > >> > >
> > > >> > > Thoughts?
> > > >> > > Karl
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Thu, Apr 9, 2015 at 7:31 AM, Alessandro Benedetti <
> > > >> > > abenedetti@apache.org>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > Of course Karl!
> > > >> > > > This is the problem :
> > > >> > > > Developing a Repo connector similar to Dropbox ( Box
> connector)
> > .
> > > >> > > > Authentication in Box is based on OAuth2.
> > > >> > > > In details after a process to grant access to your application
> > you
> > > >> get
> > > >> > 2
> > > >> > > > parameters for you Repository Connector :
> > > >> > > > Access Token and Refresh Token [1]
> > > >> > > >
> > > >> > > > To instantiate a BoxAPIConnection you need a
> > > >> Client_id,Client_secret (
> > > >> > 2
> > > >> > > > not mutable) and an Access Token and a Refresh Token (2
> > mutable) .
> > > >> > > > The access token expires in 1 hour, the Refresh Token can be
> > used
> > > to
> > > >> > get
> > > >> > > a
> > > >> > > > new Access Token, when this happens a new Access Token is
> > > produced (
> > > >> > > 1h), a
> > > >> > > > new Refresh Token is created and the old Refresh Token
> > > invalidated.
> > > >> > > >
> > > >> > > > Assuming the BoxAPIConnection object is managing properly the
> > > >> > > refreshment,
> > > >> > > > the Job will work until the BoxAPIConnection is living.
> > > >> > > > When a Job finishes ( or Manifold stop and restart) a new Job
> > will
> > > >> > start
> > > >> > > > with the old configured Access Token and Refresh Token ( that
> > are
> > > >> not
> > > >> > > valid
> > > >> > > > anymore ).
> > > >> > > >
> > > >> > > > Unfortunately we can not set for the connector the only 2 not
> > > >> mutable
> > > >> > > > params, as it is required user interaction to produce them so
> we
> > > >> need
> > > >> > to
> > > >> > > > configure all the 4 values.
> > > >> > > > We can consider the Access Token and the Refresh Token
> produced
> > > by a
> > > >> > > human
> > > >> > > > user or an external application and sent to ManifoldCF.
> > > >> > > > Using the current approach ManifoldCF should be able to update
> > the
> > > >> > values
> > > >> > > > he has to be consistent with the updated values in
> > > BoxAPIConnection.
> > > >> > > >
> > > >> > > > A bigger problem comes when both a RepoConnector and an
> > Authority
> > > >> > > Connector
> > > >> > > > are in place , but for this other complicate scenario I will
> > wait
> > > >> > until I
> > > >> > > > have a clear situation from Box itself regarding their
> > approaches.
> > > >> > > >
> > > >> > > > [1] https://developers.box.com/oauth/
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > 2015-04-09 11:53 GMT+01:00 Karl Wright <daddywri@gmail.com>:
> > > >> > > >
> > > >> > > > > Hi Alessandro,
> > > >> > > > >
> > > >> > > > > It would be great if you could describe the customer problem
> > > from
> > > >> a
> > > >> > bit
> > > >> > > > > higher level, to see if there's a better design we could
> come
> > up
> > > >> > with.
> > > >> > > > > What you have described is quite difficult to do with MCF
> due
> > to
> > > >> the
> > > >> > > > > multi-threaded and highly-cached nature of it.
> > > >> > > > >
> > > >> > > > > Thanks,
> > > >> > > > > Karl
> > > >> > > > >
> > > >> > > > >
> > > >> > > > > On Thu, Apr 9, 2015 at 5:55 AM, Alessandro Benedetti <
> > > >> > > > > abenedetti@apache.org>
> > > >> > > > > wrote:
> > > >> > > > >
> > > >> > > > > > Hi guys,
> > > >> > > > > > I have one question :
> > > >> > > > > > *ManifoldCF Version* : 1.8
> > > >> > > > > >
> > > >> > > > > > Developing a custom Repository Connector I have the need
> of
> > > >> > updating
> > > >> > > > the
> > > >> > > > > > Repository Connector config based on a Custom Listener of
> > > events
> > > >> > of a
> > > >> > > > > > custom Publisher .
> > > >> > > > > >
> > > >> > > > > > This listener will react to the publisher events during a
> > Job
> > > >> > > > execution (
> > > >> > > > > > i.e. can happen during the addSeeds or the
> > processDocuments) .
> > > >> > > > > > The listener will need to change the repository config
> > > >> accordingly
> > > >> > > and
> > > >> > > > > save
> > > >> > > > > > them in the database.
> > > >> > > > > > The main reason for this is that we need to store in the
> DB
> > > the
> > > >> > > status
> > > >> > > > of
> > > >> > > > > > the publisher, because a new Job will need to use the
> > updated
> > > >> Repo
> > > >> > > > > > Connectors config ( changed by others jobs) .
> > > >> > > > > > To simplify the problem let's assume we do not have
> > > concurrency
> > > >> > > > problems
> > > >> > > > > > right now.
> > > >> > > > > > In the future we will need to  implement a solution that
> > will
> > > be
> > > >> > > thread
> > > >> > > > > > safe.
> > > >> > > > > >
> > > >> > > > > > Cheers
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > --
> > > >> > > > > > --------------------------
> > > >> > > > > >
> > > >> > > > > > Benedetti Alessandro
> > > >> > > > > > Visiting card : http://about.me/alessandro_benedetti
> > > >> > > > > >
> > > >> > > > > > "Tyger, tyger burning bright
> > > >> > > > > > In the forests of the night,
> > > >> > > > > > What immortal hand or eye
> > > >> > > > > > Could frame thy fearful symmetry?"
> > > >> > > > > >
> > > >> > > > > > William Blake - Songs of Experience -1794 England
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > --
> > > >> > > > --------------------------
> > > >> > > >
> > > >> > > > Benedetti Alessandro
> > > >> > > > Visiting card : http://about.me/alessandro_benedetti
> > > >> > > >
> > > >> > > > "Tyger, tyger burning bright
> > > >> > > > In the forests of the night,
> > > >> > > > What immortal hand or eye
> > > >> > > > Could frame thy fearful symmetry?"
> > > >> > > >
> > > >> > > > William Blake - Songs of Experience -1794 England
> > > >> > > >
> > > >> > >
> > > >> >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > --------------------------
> > > >> >
> > > >> > Benedetti Alessandro
> > > >> > Visiting card : http://about.me/alessandro_benedetti
> > > >> >
> > > >> > "Tyger, tyger burning bright
> > > >> > In the forests of the night,
> > > >> > What immortal hand or eye
> > > >> > Could frame thy fearful symmetry?"
> > > >> >
> > > >> > William Blake - Songs of Experience -1794 England
> > > >> >
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > --------------------------
> > > >
> > > > Benedetti Alessandro
> > > > Visiting card : http://about.me/alessandro_benedetti
> > > >
> > > > "Tyger, tyger burning bright
> > > > In the forests of the night,
> > > > What immortal hand or eye
> > > > Could frame thy fearful symmetry?"
> > > >
> > > > William Blake - Songs of Experience -1794 England
> > > >
> > >
> > >
> > >
> > > --
> > > --------------------------
> > >
> > > Benedetti Alessandro
> > > Visiting card : http://about.me/alessandro_benedetti
> > >
> > > "Tyger, tyger burning bright
> > > In the forests of the night,
> > > What immortal hand or eye
> > > Could frame thy fearful symmetry?"
> > >
> > > William Blake - Songs of Experience -1794 England
> > >
> >
>
>
>
> --
> --------------------------
>
> Benedetti Alessandro
> Visiting card : http://about.me/alessandro_benedetti
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England
>

--089e0102f25a4bd06c05143ece48--