search

hashmapinc / Drillflow

A dockerized WITSML API Server that is agnostic of the backend.
Apache License 2.0
17 stars 13 forks source link

INFO NOT SHOWING THE GENERATED PASSWORD #721

Open emavworo opened 4 years ago

emavworo commented 4 years ago

After building the drillflow project successfully, I executed the jar file as stated in the manual, and its running, but going through the console logs no generated password was seen.

Testing the server using a SOAP UI brings error 401,

Anyone knows how to get this info or setting up fixed users and password?

Emma

Mike-d-s commented 4 years ago

@emavworo Emma, you can contact me via email (click my profile and my email is there) and I'll try and give you some more information. But the core of the system is to act as a facade for a backend and user names / passwords are managed by the back end system. The basic auth user names/passwords are sent to the backend system via the valve where they are validated and an auth token is generated. Drillflow uses the auth token after that.

So as coded, you need to have valid credentials on the backend and the system needs to be able to provide the token broker endpoint to accept the basic auth credentials and return the token to be used in the other queries to the backend.

Since each Valve is custom to the backend, if you want to use DrillFlow with a specific backend, you would need to modify the valve.

randypitcherii commented 4 years ago

@emavworo you might have luck using the test backend server Drilltest. I left the project a few months before development ended, so this may not work as well anymore.

Good luck!

emavworo commented 4 years ago

Thanks Randy, will try Drilltest

billydekid commented 3 years ago

@emavworo Emma, you can contact me via email (click my profile and my email is there) and I'll try and give you some more information. But the core of the system is to act as a facade for a backend and user names / passwords are managed by the back end system. The basic auth user names/passwords are sent to the backend system via the valve where they are validated and an auth token is generated. Drillflow uses the auth token after that.

So as coded, you need to have valid credentials on the backend and the system needs to be able to provide the token broker endpoint to accept the basic auth credentials and return the token to be used in the other queries to the backend.

Since each Valve is custom to the backend, if you want to use DrillFlow with a specific backend, you would need to modify the valve.

Hi Mike, I try to setup and test with Apache basic auth for an URL and put it as VALVE_BASE_URL. When I access http://localhost:7070/Service/WMLS, the basic auth I entered which popup from localhost was incorrect and seems it fails to pass to VALVE_BASE_URL.

Does my understanding is correct?