Goto project / security to the administrator tab. There you can set your MxAdmin password. Then you can log in locally with that username password combination as admin. In the cloud you can adjust it when you deploy your model.
[EDIT] This is something Mendix should fix. Create a support ticket for this issue for anyone having this problem. Is more then one ticket is created the change of it that it gets solved becomes higher.
If you are deploying to a sandbox environment you can't login as MxAdmin user, however you can login with the same role as MxAdmin. When you open up your sandbox application the app should automatically log you into the application using your Mendix ID, which you use to login to home.mendix.com and the forum. The role you are assigned is exactly the same as the MxAdmin role, there is no difference. Your Mendix ID will be the only role allowed to access the application at first. Once you have created more users in the system they will be able to login.
If you continue to have issues with this then please file a support ticket on support.mendix.com
Chris: Simon has a correct comment, when you deploy it in a sandbox 'free edition' then you will have the same role as MxAdin, commonly thats the administrator role.
in addition; once you are logged in, then you will be able to switch between users, with the user selector on the right. This option is available, when Demo users are enabled in the security settings (default enabled) This allows you to quickly switch between demo users, so that you can easily demo the app. without the need of creating users to show the app for different type of users AND logging OFF & ON on again manually.
Project settings: https://www.dropbox.com/s/as37e00pn7i3r5s/Project%20settings.png?dl=0 Select user: https://www.dropbox.com/s/ni8apa4gpogwkv9/SelectUser.png?dl=0
be aware, screenshot isn't the bounce travel app, user names and pages may differ, location & behavior is equal
If you have further questions; please post them on the forum of use the feedback button. Support ticket are to heavy weighted for this.
I am able to login locally successfully. In cloud, I am not able to login as admin. What adjustments do I need to do to make this possible?
I have the same problem... Please come back with an answer. Involves the video from section 9 "Logging in"
Same problem for me. Locally the widget can't be constructed. From the cloud I can access all if I'm logged in with my Mendix Account, but local users although they can be seen in the user management page, can't login because username and password are not correct. This goes for admin, Agent and Customers.
I think that either the LoginForm widget v3.1.1 is not playing nice with local users or either the loginform or the registerform is not hashing the password before comparing. I've hit a wall in how to continue with this. The next part in the lecture requires logging in as a customer. Any suggestions?
Solved by giving users a userrole. Without it users can't login. Still no clue for the local version though
Hello - I am stuck at the same point... Section 9 in the Bounce Travel training module. When attempting to login as instructed using the Administrator account (MxAdmin) while running the app in the cloud Sandbox, I get the "Invalid username and password". I can login with the MxAdmin user if I run local - but that worries me. The training video instructs you to run in Sandbox... http://snag.gy/RIq5b.jpg ...but I notice the browser in the training video shows the app is running locally... http://snag.gy/AbriI.jpg
When searching the forum on this issue I have seen a few responses stating that the MxAdmin user can't be used in the Sandbox (cloud), but I am not grasping why this would be, or how to deal with it, other than running the app locally. If the free version of Mendix needs to be run locally in order to enable security, I am confused by that limitation. The pricing page on Mendix.com gives me the impression I can build full featured web apps with the free edition, with the only limitation being 10 "internal" users. I assumed an "internal user" was a user with an email address that has the same domain as the address I used when signing up for Mendix. Does "internal user" mean something else, like a user that can connect to a Mendix app running locally?
My hope was to get a quick start on Mendix (by completing training) and then move to recreating custom web apps I built on another aPaas service. That service has hard data execution (ie Microflows) limits and metered add-on costs, so the unlimited feature of Mendix is appealing. I have less than 10 employees that would need to use the apps I want to recreate on Mendix, so it seemed possible to start out as a small Mendix user without paying the $15k / year fee up front. Based on my success with this first project, I would then introduce Mendix to current clients and new prospects.
How have others moved past the Section 9, part 2 logging in issue? Thanks in advance for any guidance.