-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create new admin user (clicking "Access" does nothing) #75
Comments
that's a mistake on my part, I'm trying to get a build out that has the fix, but docker.io has been having issues today. the secret is that the password is all lowercase and the user is your email. |
actually sorry, if you are running locally - I think the password should be working, but use the email address as the user. |
Sorry if I just misunderstood your replies here @aaronjudd, but I believe logging in with the auto generated user and pass from |
@lavabeams @ViktorNova - you're correct. wasn't thinking right when I first read this. I'm working on some fixes and enhancements to the site management, and access page now. |
I've closed this, as the actual screens should now work, but I've opened Issue #76, which is preventing you from adding new admin users. This process used to send emails out, pre-blaze/spacebars, and now I need to redesign this. Probably with administrable email templates. |
Aha, yes, this was my issue. In the meantime, is there a way to manually create a new user without email verification, or to at least change the username and password of the admin user? Right now my username is 'qcwydggh@localhost', which I will for sure never remember, with an equally forgettable password =) |
@ViktorNova if you do a meteor reset (or ./bin/reset) and set some ENV variables you can have the default user be the email/password you would like (from fixtures.coffee): options.email = process.env.METEOR_EMAIL #set in env if we want to supply email
options.username = process.env.METEOR_USER
options.password = process.env.METEOR_AUTH so you should add either command line, or in .bash_profile export METEOR_EMAIL="[email protected]"
export METEOR_USER="admin"
export METEOR_AUTH="password" etc. To always get the user you are wanting for default. |
That is great, thank you! Just what I was asking |
@aaronjudd Hello , first Thanks for sharing this Ecommerce , the idea is amazing... I have problem with sending email.... Maybe is my wrong , but when i set in settings menu the SMTP values using smtp.gmail.com gmail service ... After that i want to add new admin access i have following error |
@toome123 One thing you can try, you can also use If this works, perhaps the form/administrative portion is broken. In either case, if you'll open a new issue with your findings, I'm happy to take a pull request, but I'll take a look at getting it fixed in the next release if it's a new bug. |
@aaronjudd Thank's i will make sure that the problem is not in the settings, and if necessary will open issue. |
@toome123 Looks like we left the email package out in some refactor. It'll be back in 0.2.2 but in the meantime you should also do |
Can you explain again how to create a new admin user, because the answer above did not work. |
@abhisheksoni27 are you using the |
So sorry to re-live this old issue. But is a mess to be forced to validate email for example when just validating from a Docker container, There is no way to bypass this verification? as the default admin creation does but setting the email and password using ENV variables. |
@gcaracuel our docker images are running a production image. it's always going to verify the first admin user created. However in |
Any update on the ENV flag to suppress email validation? I'm using this on Heroku and have been using env settings within Heroku to set the admin user settings. I was able to manually change the validate flag to true through mLab. |
The initial admin email is set to validated by default when in development and you should receive a validation email when in production, so there shouldn't be a need to manually override anything. Worst case, you could edit the record in the database, but I don't really see why that would be necessary when all you have to do is click the validation link that gets emailed to you. |
Maybe I am missing something here, but how do you get a verification email through the initial deployment if you have to login as admin and hook something like Sendgrid in order to get said verification email? |
You can set the mail with the a https://github.com/reactioncommerce/reaction-docs/blob/development/admin/email.md#advanced |
hey guys, i am running on heroku, i created the environment variables on my running app, but i cannot get a admin user? i looked into the mongodb but the created password is encrypted. How to create a new admin user? |
…ws-7.4.6 chore(deps): Bump ws from 7.2.5 to 7.4.6
Hello! I just installed a new instance of Reaction without a hitch, sweet!
I don't see a way to change my admin user from the gibberish that was auto generated on the first run, am I missing something?
I tried clicking on "Access" in the dashboard, and it didn't have any effect
The text was updated successfully, but these errors were encountered: