[ 
https://issues.apache.org/jira/browse/GRIFFIN-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lionel Liu updated GRIFFIN-223:
-------------------------------
    Comment: was deleted

(was: Hi [~dna.dgw.engg], I still think it is some issue about lilvy 
authentication. Maybe you can write a sample application to test spark job 
submission through livy server in java way.
We have not deployed such a livy server requiring authentication, thus we are 
not familiar with such an issue, maybe the livy community could answer this 
question better.
You can tell us how's your livy server deployed, we will also have a try to 
deploy such a livy server in secure environment, and enhance the job submission 
part. )

> "Post to livy error. 401 Credentials missing or Auth is not Basic"
> ------------------------------------------------------------------
>
>                 Key: GRIFFIN-223
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-223
>             Project: Griffin (Incubating)
>          Issue Type: Bug
>    Affects Versions: 0.2.0-incubating
>         Environment: Azure HDInsight
>            Reporter: Infosys
>            Priority: Major
>             Fix For: 0.2.0-incubating
>
>         Attachments: Griffin_FOUND.jpg, Infolog1.log, 
> Infosys_griffin_livy_session_codechanges_0103.log, Log.log, Log2.log, 
> griffin_livy_session_log_0103.log, log1_05Dec2018.log, log2_05Dec2018.log, 
> log7.log
>
>
> Hi
> We are getting error ""Post to livy error. 401 Credentials missing or Auth is 
> not Basic" for Griffin installed on Azure with HDInsight Cluster. below curl 
> command is successful but we are unable to get Livy working.
>  
> curl -k --user "admin:admin" -v -H "Content-Type: application/json" -X POST 
> -d '\{ 
> "file":"wasb://[email protected]/apps/griffin-measure.jar",
>  "className":"org.apache.griffin.measure.Application" }' 
> "https://xxxxxx.azurehdinsight.net/livy/batches"; -H "X-Requested-By: admin"



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to