I set up a gitlab server in ubantu14.4.3SLT
in my case, I want to set up a git server for local users so I do not need user to sign in with any email confirmation.
How can I disable email confirmation in gitlab? are there any api or something simple to disable it?
This isn't a good answer. But ran across this and wanted to skip for a test instance I have. This is what I did(gitlab 10.1.0):
From the rails console:
User.all.each {|u| u.confirmed_at = Time.now; u.save}
Related
After reinstalling windows on my machine, i have tried to login to my Github account using the same user-name password stored in the browser with my Microsoft account...
with Sign in to GitHub
Username or email address page:
its seems to accept the credentials (tried with email as well with username) and then navigate to the next page saying:
Device verification code
We just sent your authentication code via email to y**************#hotmail.com.
But I never receive any email!!!
not in inbox or junk email beside the GitHub Community Summary..
i am afraid to try the Forgot password option - because perhaps it get the auth issue even worse.
Resetting the password seems to be a solution.
The email should arrive within a few minutes in case of setting a new password, even if you had problems in the authentication process.
So my goal is to create a Rundeck job that runs on a schedule and isn't run as my personal user, or any "regular" user, but rather a bot user. Ideally this bot user wouldn't have login access and restricted permissions for security reasons, but would be able to run certain jobs. I've tried searching, but the only information I'm finding is about how to create a "regular" user in Rundeck. Even if I go down that route of creating the bot user as a "regular" user, to use it, you need to pass in either the login credentials or an API token. An API token would be fine, if it could be generated and pulled in on the fly. However, that is not the case, the API has an expiration itself. If there is something I'm missing, please let me know. I'd love to get this working.
Rundeck Version: Rundeck 3.2.1-20200113
Rundeck Cli Version: 1.1.7
You can set the following configuration in your rundeck-config.properties file (usually at /etc/rundeck/ directory):
rundeck.api.tokens.duration.max=0
This will disable your maximum period, you can see this in the official documentation here.
With that, your "bot user" can do it through API / RD CLI as you wrote.
Try using webhooks https://docs.rundeck.com/docs/manual/12-webhooks.html
You can trigger a job by making a http-request
The way I've implemented bots is as a user who is a member of a 'bot' user group, with ACLs that lock down that group as required. Any passwords required for the scheduled job are loaded into the key storage of the bot user.
With this approach you still need someone who knows the bot credentials to login as them and set passwords/SSH keys, but that's a one-off. Is that what you're trying to avoid?
The one annoying thing I've found is that a scheduled job always seems to run as the last user to edit the job - so I grant edit access to bot users and make sure to set/reset the schedule after any edit by a normal user. Hoping to address this through https://github.com/rundeck/rundeck/issues/1603, you might want to give it a 👍.
We had a fully working Jira Service Desk installation (JIRA Service Desk Application v3.6.1) for years and on Friday we changed the password of the associated email account ithelp#...
Once the change was done on the Exchange server we updated the password on system-Outgoing Mail and system-Incoming Mail, provided the latest password by clicking on checkbox adjacent to Change Password. After entering the password, click on Update button.. The test in both cases says its working.
If we check Mail audit log for ithelp#... then we see.
If we do a test there then:
And the "view log" shows:
What have we tried?
We went through https://confluence.atlassian.com/jirakb/troubleshooting-jira-service-desk-incoming-mail-790960076.html?_ga=2.74568658.1933816762.1551665594-977289960.1550604024 without success.
Restarting Tomcat.
Rebooting the server.
Deleting and recreating the configuration for IMAP.
Configuring the IMAP settings using IP instead of server name.
If you know what could be the problem or if you know what we are missing your help is greatly appreciated.
Thanks in advance,
Log into Jira Service Desk with elevated rights. (administrative rights)
Select projects -> IThelp
Select email requests.
Under custom email addresses click the edit.
Change the password to the new password set for IThelp. Click next
Select the email request type as Email Request
Our jenkins server has a lot of jobs, is there anyway to configure so that an email is sent when any build breaks? I know how to do it for each job individually, but I'd like to set up a global configuration.
We use the Email Extension Plugin.
and then configure our SMTP Server in the General Configuration.
Once this is all setup, then add a Post Build event in your Jenkins job to send an email on failure.
We ended up using this https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin
There is a way to configure emails for all jobs at once
I installed gitlab 6.2 on my server as seen here installation.md
When I add a user via web interface the user receives the mail send by gitlab.
But without password.
The Administrator created an account for you. Now you are a member of the company GitLab application.
login.......................................... sample#domain.com
password..................................
You will be forced to change this password immediately after login.
Click here to login
When I change the password of the user manually in the admin panel the login is successful.
In my gitlab.yml I have this:
## Users management
# default: false - Account passwords are not sent via the email if signup is enabled.
# signup_enabled: true
There is currently a bug in Gitlab 6.2. There is already a a bugfix for that in master branch: https://github.com/gitlabhq/gitlabhq/pull/5436
You can apply this change manually to fix the problem.