Sounds good. All pull requests are welcome.
On Tue, Mar 13, 2018 at 6:52 AM, Alan Camillo wrote:
> We were able to run Fluo with Kerberos without big problems.
>
> Suggestions: add some properties on fluo-app to informe principal, keytab
> and the other necessary attributes related to Kerberos.
We were able to run Fluo with Kerberos without big problems.
Suggestions: add some properties on fluo-app to informe principal, keytab and
the other necessary attributes related to Kerberos.
Alter the code to authenticate properly using this parameters.
If you agree, we are going to open a issue
On Tue, Mar 6, 2018 at 6:01 PM, Alan Camillo wrote:
> Ok! I am!
> I'll document all the changes needed and submit a pull request if necessary.
That would be really cool.
>
> Thanks!
>
> Alan Camillo
> *BlueShift *I IT Director
> Cel.: +55 11 98283-6358
> Tel.: +55 11 4605-5082
>
> 2018-03-06 16:
Awesome!
On Tue, Mar 6, 2018 at 6:01 PM Alan Camillo wrote:
> Ok! I am!
> I'll document all the changes needed and submit a pull request if
> necessary.
>
> Thanks!
>
> Alan Camillo
> *BlueShift *I IT Director
> Cel.: +55 11 98283-6358 <+55%2011%2098283-6358>
> Tel.: +55 11 4605-5082 <+55%2011%2
Ok! I am!
I'll document all the changes needed and submit a pull request if necessary.
Thanks!
Alan Camillo
*BlueShift *I IT Director
Cel.: +55 11 98283-6358
Tel.: +55 11 4605-5082
2018-03-06 16:20 GMT-03:00 Christopher :
> I don't know that anyone has tried Fluo on a Kerberized cluster yet.
>
I don't know that anyone has tried Fluo on a Kerberized cluster yet.
On Tue, Mar 6, 2018 at 9:33 AM Alan Camillo wrote:
> Are there someone working with Fluo in kerberized clusters?
> Does it woks? Should I adapt this kind of code to login using Kerberos?
>
>
> https://www.dropbox.com/s/vn7c9mwf
Are there someone working with Fluo in kerberized clusters?
Does it woks? Should I adapt this kind of code to login using Kerberos?
https://www.dropbox.com/s/vn7c9mwf8u2jqr5/hlpUXniG48lSezGG6zY7v5-24WrxJtzJ-YyGGUk5pp1iHHpqyMySIJcXFMUlZV8sxikt4iniAFPrstEZIjH3Kb8VmMbJqLp2QBfO6bgRROpcaGLbLOj-naEHv1HW