Should the API expose every authentication strategy implemented in Oak? How is this API should look like?
2015-01-27 10:39 GMT+01:00 Stefan Guggisberg <[email protected]>: > On Tue, Jan 27, 2015 at 10:16 AM, Francesco Mari > <[email protected]> wrote: >> Which other alternatives do we have regarding authentication? > > remote and local users should IMO use the same credentials. it should > be transparent to the user whether he's accessing a local or a remote > repo. > > cheers > stefan > >> >> 2015-01-27 9:16 GMT+01:00 Stefan Guggisberg <[email protected]>: >>> hi francesco, >>> >>> On Fri, Jan 23, 2015 at 6:09 PM, Francesco Mari >>> <[email protected]> wrote: >>>> Hi all, >>>> >>>> since I don't have access to the wiki, I started to write down a draft >>>> for the remote API in a public GitHub repository [1]. >>>> >>>> I didn't write much so far, but I invite every interested party to >>>> take a look at it for suggestions and improvements. >>>> >>>> Thanks, >>>> >>>> Francesco >>>> >>>> [1]: https://github.com/francescomari/oak-remote >>> >>> "To access the Oak Remote Interface a client needs to have the >>> credentials of the master user." >>> >>> are you saying that a client needs master user credentials to access a >>> remote oak instance? that would IMO be wrong. >>> >>> cheers >>> stefan
