[ 
https://issues.apache.org/jira/browse/METRON-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785566#comment-16785566
 ] 

Tobin commented on METRON-2024:
-------------------------------

I’ve reformatted my stellar.rest.settings map to match yours and can now see 
the Basic Auth in tcpdump.

In tcpdump, my…

REST_GET("http://metron.node:8082/api/v1/global/config";)

…request/response now looks like my…

curl –u admin:admin "http://metron.node:8082/api/v1/global/config";)

…request.

But, whereas curl displays the response as expected, Stellar displays nothing.

So, we’ve taken a step forward but there’s still no output or error from 
Stellar. Any ideas? Would it be possible for you to repeat your test against 
api/v1/global/config ?

Thanks,
Tobin

From: Ryan Merriman (JIRA) <[email protected]>
Sent: 05 March 2019 16:07
To: Landricombe, Tobin <[email protected]>
Subject: [jira] [Commented] (METRON-2024) REST_GET function ignoring Basic Auth 
settings


[ 
https://issues.apache.org/jira/browse/METRON-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784607#comment-16784607<https://issues.apache.org/jira/browse/METRON-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784607#comment-16784607>
 ]

Ryan Merriman commented on METRON-2024:
---------------------------------------

Here's my use case:
{code:java}
[root@node1 vagrant]# /usr/metron/0.7.1/bin/stellar --zookeeper node1:2181
Stellar, Go!
Functions are loading lazily in the background and will be unavailable until 
loaded fully.
{es.clustername=metron, es.ip=node1:9200, es.date.format=yyyy.MM.dd.HH, 
parser.error.topic=indexing, update.hbase.table=metron_update, 
update.hbase.cf=t, es.client.settings={}, profiler.client.period.duration=15, 
profiler.client.period.duration.units=MINUTES, 
user.settings.hbase.table=user_settings, user.settings.hbase.cf=cf, 
bootstrap.servers=node1:6667, source.type.field=source:type, 
threat.triage.score.field=threat:triage:score, enrichment.writer.batchSize=15, 
enrichment.writer.batchTimeout=0, profiler.writer.batchSize=15, 
profiler.writer.batchTimeout=0, 
geo.hdfs.file=/apps/metron/geo/default/GeoLite2-City.tar.gz, 
asn.hdfs.file=/apps/metron/asn/default/GeoLite2-ASN.tar.gz, 
stellar.rest.settings={basic.auth.user=user, 
basic.auth.password.path=/user/metron/password.txt}}
[Stellar]>>> 
REST_GET('http://httpbin.org/basic-auth/user/password<http://httpbin.org/basic-auth/user/password>')
{authenticated=true, user=user}
{code}




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

________________________________________
Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.Part 
of the Chemring Group. 
Registered in England & Wales. Registered No: 00267550
http://www.roke.co.uk
_______________________________________
The information contained in this e-mail and any attachments is proprietary to 
Roke Manor Research Limited and 
must not be passed to any third party without permission. This communication is 
for information only and shall 
not create or change any contractual relationship.
________________________________________


> REST_GET function ignoring Basic Auth settings
> ----------------------------------------------
>
>                 Key: METRON-2024
>                 URL: https://issues.apache.org/jira/browse/METRON-2024
>             Project: Metron
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Tobin
>            Priority: Major
>
> In Zeppelin:
> %stellar
> swagger_conf := \{ "basic.auth.user": "admin", "basic.auth.password.path": 
> "/user/zeppelin/swagger_pass" }
> REST_GET("http://metron.node:8082/api/v1/sensor/enrichment/config/bro";, 
> swagger_conf)
> It returns with no response and no error.
>  
> Zeppelin logs show the normal "status 401" and "unauthorized" messages from 
> Swagger.
> tcpdump shows no "Authorization" header in the request.
>  
> I can't find anything else in the zeppelin, metron-rest, etc logs.



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

Reply via email to