Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Username/Password not found issue with corb #538

Closed
RobertSzkutak opened this issue Oct 8, 2015 · 7 comments
Closed

Username/Password not found issue with corb #538

RobertSzkutak opened this issue Oct 8, 2015 · 7 comments

Comments

@RobertSzkutak
Copy link
Contributor

Saw this with a client. If you have roxy setup to prompt the user for a username/password rather than have one in your *.properties file corb will give an error that there is no default username and password available to it.

I'll try to set aside some time and see if I can get a fix in the not too distant future.

@grtjn
Copy link
Contributor

grtjn commented Oct 9, 2015

Having a prompt_password in there makes a lot of sense. Keep in mind prompt_password stores the value in @ml_password. You can also make it prompt for the user if I am not mistaken..

@grtjn grtjn modified the milestones: 1.7.3, 1.7.4 Oct 9, 2015
@jmeekhof
Copy link
Contributor

I'm seeing a very similar issue. In my case I'm using mlcp.

In our environment, we use app_specific.rb to inject username and passwords from the environment variables. This method of setting username and password is working for all the normal deployment commands.

The actual issue I'm seeing, is the -option_file replacement is not occurring for the @options that are set in the app_specific.rb.

@grtjn
Copy link
Contributor

grtjn commented Oct 12, 2015

@jmeekhof, can you show what you are using inside the options file contents? Something like ${app-name} gets replaced properly at my end. @ml.app-name should work too. Maybe you forgot the ml. prefix that is necessary with the @ notation?

FYI: -option_file is a typo, and should have been -options_file. I prepared a fix for Roxy to change that.

@jmeekhof
Copy link
Contributor

Ok, I have a clearer picture now.

When I was attempting the first time, I had been using tho @ml.user syntax as a command line parameter. Now that I've looked at the code, I see why that didn't work. I've now put my information into a file, and the command seems to be work (I also changed the code to look for the -options_file parameter instead of -option_file).

One clarifying point is the ./ml {env} mlcp command only can find the options file in the deploy directory. Shouldn't we allow the option file to live anywhere?

@grtjn
Copy link
Contributor

grtjn commented Oct 12, 2015

The path can be relative, so you could go up with ..

I think i have a pr open that makes the roxy look from project root instead..

@RobertSzkutak
Copy link
Contributor Author

Pushed in a fix to my open pull request: #567

dmcassel added a commit that referenced this issue Mar 4, 2016
Bootstrap and wipe granularity and #538 Fix
@RobertSzkutak
Copy link
Contributor Author

Closing as my PR to fix this was accepted

@dmcassel dmcassel modified the milestones: 1.7.3, 1.7.4 Mar 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants