I'm going to work on project, that uses plastic scm for version control. Project manager sent me a message with repo address, my username and generated (at least it looks like randomly generated) password. I'd like to change the password as it seems like a good safety practice to me. I tried to sign in on www.plasticscm.com, as I assumed that manager just created account for me, but I can't log in. Is this possible to change my password, or do I have to ask admin for help?
It's important to clarify if you need to:
Change your www.plasticscm.com password: You just need to click on the "Sign in" button and then "I don't have a password / I forgot it". You will receive en email to re-generate the password.
If you are using a Plastic hosted server: we have recently released a webadmin tool where you can configure and administer the server, including selecting the authentication mode, creating users and groups (or edit the passwords):
http://blog.plasticscm.com/2017/10/webadmin-introducing-new-server-admin.html
Related
In the terminal I executed this command:
amplify pull --appId d2nb7sae2nlt33 --envName staging
which gave me this response in the termina:
Opening link: https://us-east-1.admin.amplifyapp.com/admin/d2nb7sae2nlt33/staging/verify/
Continue in browser to log in…
In the browser, I'm asked to enter a username and password. I enter my aws root username and password, and I'm told they're incorrect. That username/password works everywhere else in AWS.
Am I supposed to set up some other user name/password for AWS Amplify?
The answer in my case was:
1 You should be clear about which backend you are using. If you have two backends, then d2nb7sae2nlt33 above may not refer to the backend where you have set up your credentials, and
No, the root user is not what you need to enter. The app needs to have an admin user set up. You set it up with a user, which sends an invite to an email, and you respond with a temp password, then set it up with a real password.
go to https://console.aws.amazon.co/amplify (there may be more, like the region, but that's the general idea)
then from the side menu go to Admin UI management under App Settings.
then Invite Users, big orange button in Access Control Settings.
This should get you on your way.
I am a hardware guy first and software second so GitHub is not my forte.
I had Altium Designer setup with my GitHub server for version control. When GitHub forced 2FA recently it broke the link to Altium which, unfortunately doesn't have stellar GitHub integration.
There are 6 fields I am allowed to enter in Altium to point it to my (GitHub) server:
1.) Method (HTTP, HTTPS, file, svn)
2.) Server (URL)
3.) Port
4.) Repo Subfolder
5.) username
6.) Password
Again, nothing changed except moving to 2FA. Now, when I attempt to login it obviously says it could not connect to the server because Altium has no provisions to provide a token during the login process.
I read the article at GitHub here: https://docs.github.com/en/free-pro-team#latest/github/authenticating-to-github/using-ssh-over-the-https-port
But I have no idea if that will do anything for me. Is there a way to route my Altium server connection to use my SSH key outside of the Altium environment? Or perhaps another way to "whitelist" my desktop in GitHub for SSO?
GitHub has not forced 2FA on for users. That wouldn't be useful, because people could just not set up a second factor. It's possible your organization has required this, though.
However, GitHub is deprecating the use of a plain password when using Git over HTTPS in favor of a token. Using a plain password was already forbidden for users who use 2FA, since there's no place to send a 2FA code (and for automated systems, doing that would be very inconvenient).
In this case, it's easy to keep using HTTPS: just generate a personal access token (in the developer settings) with the repo scope and paste it into the password field. Git doesn't know the difference between a password and a token; they're both the same to it. This also has a bunch of other benefits:
If you change your password, the token isn't automatically cleaned up, so you don't have to change Altium Designer.
If you decide you want to revoke that token, you can do so independently of changing your password.
If you're using SSO, you need to enable that token for SSO using the drop-down before it can be used to access protected resources.
I have a running prosody that handles XMPP for a couple of my domains, and a friends domain. One of the users (his wife) on my friend's domain would like to change her password (actually she has forgotten her, so I would set one with prosodyctl that she should then change to something I don't know). But when I try changing the password of a test user I created on that domain through pidgin, I get an error saying "Error changing password", "Service unavailable". What do I need to change to allow users to change passwords?
I found the needed clue in The ArchLinux wiki on prosody, even though it claims it to be the default (it might be on Arch, it wasn't on my Debian), I needed to enable the register module, and make sure allow_registration was set to false.
I opened a demo xsp page and a window popped up asking me to input the name and password to login to the domino server. Then I entered my own id and password created in domino, but it didn't work. Only the Administrator name and its password worked. Anybody knows what's the problem? I already edited the corresponding ACL entries.
Thanks!
In order to use a database in a browser (no matter if classic notes web development or Xpages) one needs to meet several requirements.
First of all you need access to all NSF files that are used in the process.
As mentioned by Richard you either need to be mentioned in the ACL (namely or by group membership, or by setting -Default- and/or Anonymous to a level greater than No access).
AND the ACL has to allow Web- Access by not setting the Maximum Internet Name and Password to No Access
But this is not enough.
To be able to do authentication you do not have an ID- file in the browser.
You need a username and password. This password is NOT the password of your ID- file unless the admins choose to synchronize them using a policy.
It is the password stored in your person document in the names.nsf on the server.
But still these points are not enough yet: If you have access to the server with your username and internet password (can be tested by just trying to login to http://yourServer/names.nsf?open&login), then you might still not be able to access the application if -as umeli pointed out in the comment- the signer of the Xpage- application does not have enough rights to sign the XPages (Server document - security).
You see: There is a lot stuff to check. But if all of these points are OK, then access to the database will not be a problem anymore.
I omitted one reason for not beeing able to login because of your error description: If the Session Authentication on your server is configured for Multiple Servers (SSO) then you need to use the fully qualified internet host name of the server in the URL (or at least a hostname, that contains the SSO- domain), otherwise you will be redirected to the loginpage over and over again, even after supplying the right username / password. But as you wrote about a "Window popping up" I am quite sure, that Session authentication on that server is set to "Disabled"
You could be being rejected because of the
ACL of the NSF file not having the level of access required for operations performed in the code on the Xpage. I know you said you edited the ACL, but bear in mind that access also depends on the 'Maximum Internet Name and Password' setting for the NSF.
ACL in other NSF files that are accessed in the code of the Xpage not having the level of access required for operations performed on it by the code. This also includes the 'Maximum Internet Name and Password' setting.
Now, I am trying to use Collabnet Subversion Edge authentication with Active Directory. At that, I found a problem.
Some user in AD can enter into Collabnet and some are not. Actually, all user in my AD server are created by script. So, all configuration except username and password are equal. But some cannot enter into Collabnet. So, I check the collabnet log. It shows "Password Mismatch" error for all invalid user. But we type the right password.
And then we test by changing account password. No changes. Then, I created a new account and log-in into Collabnet. It is OK. I don't know what should do.
Summary, In my authentication with AD, Newly Created user can log-in into Collabnet, Old User who success first time can also log-in and some user are always "Password Mismatch" even I type right password. I tried every possible way what I think, but It is not work.
Anyone faced like this one? Someone Help me. Thanks.