We have JIRA for our faculty/staff at the college I am applications developer for. The JIRA is fine-tuned for them to report issues to maintenance and I.T. We use LDAP for external authentication of user passwords.
Right now, if someone new joins our company, I have to manually add a new user to JIRA. I am wondering if there's a way to create a batch process that checks the LDAP, and if there's a new user, automatically creates a user account on JIRA for them. Has anyone done this before?
What version of JIRA are you using.
Version 4.3.x has simplified the user directory configuration quite a bit, including the support for creating a JIRA user at first login
Check out following article
http://confluence.atlassian.com/display/JIRA043/Connecting+to+an+LDAP+Directory#ConnectingtoanLDAPDirectory-AddingUserstoGroupsAutomatically
Francis
Related
Hello I'm having some issues with accessing my wp-admin after migrating a website onto a Chinese server.
I used WP Migrate DB plugin to ensure all mentions of my old domain was replaced with the new domain.
I deactivated plugins, changed the theme, created a new admin user, checked user roles and a few other possible solutions that I can't recall at this time.
Looking for general ideas on how to resolve this that I might not have tried.
Thanks
Until now I was using my free personnal account to develop with Codename one. I couldn't send my builds anymore because I have reached the 1MB limit. Now my compagny bought a basic subscription and I would like to use it but I can't: when I send my build the server, it tries to send it with my personnal account. I tried to solve that issue downloading a new eclipse version but it doesn't work.
How can I sent my builds using my new basic account ?
You can solve this by changing the password of your free account here, which will prompt you for new login details when you send a build... then you can enter your basic account details when prompted.
Note: Codename One may suspend your basic account if they discover it's been used by multiple users within your company. They have one account one user policy, so don't abuse it. The only account that MAY be shared by multiple developers within a single company is an Enterprise account.
I was develop and application, which can produce number of associated table if for a user and when user select appropriate client he can view report based on user id, password and table id.
Now, google change authentication process and introduce Auth2.x process to authenticate a user.
Is there any body who can help me regarding this problem, this will be a great help.
I am a .net developer so any help in dotnet will be much appreciated.
Thanks a lot in advance.
Take a look at this link https://developers.google.com/analytics/resources/articles/gdata-migration-guide. Look at section "Create a Project in the Google APIs Console" it will walk you through the whole process. This is what I used and it helped.
We are looking to use an Active Directory server to restrict access to certain URLs in our Spring application on a Weblogic server and I have no idea where to start. The problem should be quite simple as I understand it, we have a simple app which has a number of URLs:
<root>/page1.do
<root>/page2.do
<root>/page3.do
etc.
And an Active Directory servers which lists the users in two groups, such as "Admin" and "User". We would like it so that based on the login information provided (no SSO required), anyone in "Admin" can access all pages, anyone in "User" can only access page2.do and page3.do.
I have absolutely no idea where to start and Google isn't being very forthcoming. I would have hoped that this is an easy task (add AD server to weblogic, set up a config file). Anyone have any experience with this and links to good places to get started or a summary of what we will need to do to get it working in this fashion?
Cheers
You should be able to easily use your AD as an Authentication Provider in your Weblogic server(s). Here is some documentation to get started on how to do the configuration:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/atn.html#wp1198953
After that, you can configure security roles and security policies in order to control access to your server's resources. Again, some docs to get started: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/secintro/concepts.html#1083616
If you prefer a good book to start with, here goes my suggestion: http://onjava.com/pub/a/onjava/excerpt/weblogic_chap17/index.html. Although somewhat old, this chapter covers pretty much everything you need to know.
I am developing a web based intranet for my company. I just want to know is it a good thing for users to login the application using the active directory login details or shall i create a login together with the application db.
If there is anything better that this please suggest. This is my first application development so need help from experienced people.
Generally it's a good idea to try and minimize the number of accounts people need to have.
So I'd definately try and use their active directory login.
Also if desireable, you can automatically log people into your application using various single sign on methods. (Either integrated into IIS, or other.).
This makes for a very usable application, as people always forget login details, and hate to login again to other systems.
Only use Active directory for your intranet, if you infrastructure supports it.
You question is phrased as if you think the user to type there password in again to login to the intranet site - they should not do this! have windows pass on the credentials automatically. This is pretty much built in to dotnet/iis/etc.
Also AD will add group management a privledges so you can restrict areas of you intranet to members of certain groups.
And you support team already have the tools to manage all this.
PS you can enable FireFox to auto log on via NTLM and it is one of the most requested features for Chrome too so don't let browser issues put you off
There are several pros using Active Directory authentication in the intranet.
Thoses are the main ones:
You want to to keep authentication stores number as low as possible
Using Active Directory, users who have their desktop in the domain (as they should) will be able to use Integrated Windows Authentication. They will be able to log in without having to type their password.
An Active Directory authentication mechanism probably exists for your language
More information:
http://msdn.microsoft.com/en-us/library/ms998358.aspx
If you create a separate login system, then your users have to remember 2 different logins. Why bother, when their "real" login is right at hand?
Less code for you to write and better integration into the wider system. And, who doesn't want FEWER passwords to remember.
Definitely go for the Active Directory option, or use Active Directory as an LDAP server if whatever language you're using doesn't directly support AD. Active Directory actually makes a pretty good LDAP server.
If there is anything better that this please suggest.
OpenID?...