I'm using microk8s with kubeflow on ubuntu 20.4. When I deploy kubeflow for the first time using the cmd "microk8s enable kubeflow", it gives a user id and password, and dashboard URL. but when I go to the URL, it shows a login page with email and password fields. so how can I get the "user-id" field here instead of email? I also have tried default "admin#kubeflow.org:123456", also not working.
user id is equal to the email filed here. so just paste your user id in the email filed.
Related
I have a rails app and I have implemented devise, password resets etc that are built into devise.
I have a username field, however, I now need to allow the user to reset this too from the login page following the same flow as the way devise does password resets (recoverable).
I have a forget page where the user can select whether they have forgotten their password or username, the password flow is built-in devise, however, I'm unsure how to go about doing the username reset.
I have the views, but I need help with the backend so the flow I need is the user clicks that they have forgotten their username, they enter their email, they get sent a username reset email with a link with a generated token, clicking that link should send them to a page where they can reset there username.
Some images for reference
Any help here would be great.
#debugabug I think it can be an api call when user clicks on forget username or forget password. Having code common for both is better than to duplicate it.
The API call is a POST call with email address in case of 'forget username' or username in case of 'forgot password'. Based on the incoming parameter, backend can decide the next workflow.
We have a asp.net MVC site. We want our users can log in to MediaWiki by their user name and password without sign up for MediaWiki. How can we do that?
This is exactly what we want:
our users go to the Media Wiki login form (they have no account in Media Wiki).
they fill the username and password input by their username and password(the username and password which they use to login to our website).
the username and password have to be sent to our website API link:
ourSiteDomain.com/Api/GetPersonRow?UserName=$userName&Password=$password
The $username and $password are filled in step 2.
Our API returns a JSON response with user info without password.
if the user is really our user and API response returns true, the user can log in to Media Wiki.
These steps are what we want.
I don't know how to do these steps.
You'd have to write a PrimaryAuthenticationProvider. XenForoAuth and IPBAuthLogin are some examples.
Between the Active Directory Plugin and the Build User Vars Plugin i use the email attribute field so we send email messages about jobs after they have run.
Currently Ad is integrated and populates the user's details and the Build user vars plugin takes the email from this user's account to send the mail.
Does anyone know how i can change the AD lookup attribute to something else for email? I did try to manually modify the email on the user's account but it keeps getting reset to the old value. Modifying it in AD isn't an option as i would like to redirect the attribute for all users.
I upgraded to the latest version of the AD plugin which allows modification of email address.
I'm working on a project in WebStorm that's hooked up to Bitbucket for version control. Every once in a while I get a prompt to log into my repository and there is link on the bottom suggesting I use a Bitbucket app password. I have an app password on Bitbucket, but can't find anything on the web about how to integrate WebStorm with the app password.
If your repository is at https://bitbucket.org/username/repo.git then the username field is to be filled with the username part in the URL and the password is your created app password.
Instead of typing your account username and password in the dialog, type your app password's id in the username field and your app password's password in the password field.
We are using OAuth in our apps to login to repositories such as Google Drive, OneDrive and Box.
We allow the option for the customer to create a default user, so we use login_hint parameter to pre-populate the default user. Since the box with pre-populated username is editable, if the customer decides to modify the username, and tries to login with a different username the page is reloaded with the default username again, instead of logging in. On the second attempt the user is able to login with the new username.
Is this a known behavior? I would expect the user to be able to login the first time. This also works inconsistent, sometimes user is able to login with modified username from the first attempt.