Menu

#45 AD authentication

version 0.8
closed
nobody
None
1
2019-04-19
2013-11-12
Anonymous
No

Hi there, great product and much appreciation for what you are doing!

Wondering about how to configure AD authentication, just a nudge in the right direction is all we need.

Thanks!

Discussion

  • Miha Petkovsek

    Miha Petkovsek - 2013-11-13

    Hi, well it should be simple enough:

    1. administration > settings > Auth type > set to AD authentication and save settings
    2. administration > AD connection settings appear, there you can set AD connection parameters. If you want to search for domain users you have to add admin/pass also
    3. add new user, set user type as domain and username same as in domain

    thanks should be it.

    brm

     
  • Anonymous

    Anonymous - 2013-11-25

    There seems to be an issue with AD where the username is the same as the first name of the user auth fails

     
  • Anonymous

    Anonymous - 2014-02-28

    With the settings you have suggested above, I still fail to authenticate despite that the AD testing in the config has passed.

    *** Error *
    Can't contact LDAP server
    Failed to authenticate user against AD!
    *****

    My settings:
    Base DN: CN=sv_user,OU=SvAccounts,OU=AltUserAccounts,OU=UserAccounts,DC=,DC=
    Account suffix: @***.com
    Domain account: sv_user
    <password>
    Use SSL: false
    Use TLS: false
    AD port: 636

    Test settings: shows "AD network connection ok!"

     
  • Miha Petkovsek

    Miha Petkovsek - 2014-03-03

    Are you entering the user/pass correctly (upper/lowercase)?

    Tests show that nw connectivity is ok, user auth seem to be failing. Can you see any errors on AS side?

    I can write a small script to test your settings?

     
    • Anonymous

      Anonymous - 2014-03-20

      Turned out that it didn't support port 636. Only supported port right now is the default port 389. Changed to port 389 and everything works great.

      Just out of curiosity, is there any plan in the future for non-default LDAP ports support?

      Thanks Miha

       
  • Anonymous

    Anonymous - 2014-03-20

    Turned out that it didn't support port 636. Only supported port right now is the default port 389. Changed to port 389 and everything works great.

    Just out of curiosity, is there any plan in the future for non-default LDAP ports support?

     
  • Miha Petkovsek

    Miha Petkovsek - 2014-03-24

    Hi, I use ADldap (http://adldap.sourceforge.net) for AD authentication. I believe custom ports should work.

            $adldap = new adLDAP(array( 'base_dn'=>$ad['base_dn'], 'account_suffix'=>$ad['account_suffix'], 
                                        'domain_controllers'=>$ad['domain_controllers'], 'use_ssl'=>$ad['use_ssl'],
                                        'use_tls'=> $ad['use_tls'], 'ad_port'=> $ad['ad_port']
                                        ));
    
     
  • Jim Julson

    Jim Julson - 2015-09-06

    Hi Miha,
    I know this post is a little older, but I'm having a heck of a time finding solid documentation on how to properly make use of AD Groups and AD Auth together. From what I've conjured up thus far, here's what I've come up with. I'm hoping you can validate this.

    BASIC AD SETUP

      1. As stated above, get the PHPIPAM instance setup to use AD.
    1. Create your AD User locally in PHPIPAM first that will be used for BINDING to AD
    2. Set AD as the Authentication type, then proceed to the Active Directory section
    3. Fill in all necessary details, and ensure you use the user you created locally as the ad-binding (Was setup as "Active Directory" as the type
    4. At this point, basic user access is there to auth against AD.
    5. Create new users in PHPIPAM that are "Domain" type users.

    BASIC GROUP PERMISSIONS

    1. Create groups locally within PHPIPAM. These do not match to ANY Active Directory groups (That I can see)
    2. Add the users that you setup locally as "Domain" users to any local groups that you have setup (Whether the default ones, or custom ones).

    Does that about sum it up?

    This functionality is a great start, however, the flaw here is for those of us that have MANY instances of PHPIPAM. Our org is VERY large, so we have to have a different instance per product so to speak. This means we have to manage 10 different instances as things are now. If proper AD Group Membership could be queried, and we didn't have to rely on LOCAL user creation, then we could simply create AD groups, place users in groups, and that would give them permissions automatically based on group membership.

    Am I missing something somewhere? Is that how this is supposed to be? Sorry if this is a silly question. Thanks in advance for your time. Keep up the amazing work!

     
  • Miha Petkovsek

    Miha Petkovsek - 2016-02-02
    • Status: open --> closed
     
  • Anonymous

    Anonymous - 2017-03-17
    Post awaiting moderation.
  • Anonymous

    Anonymous - 2019-04-19
    Post awaiting moderation.

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.