Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

K

Marshall Chen

@kx001
Unfollow Follow
About
Posts
4
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Retrieve data FROM NetXMS
    K Marshall Chen
    Support

    Quick question is where to get the help content for REST APIs.  https://wiki.netxms.org/wiki/Web_service_API is too simple.


  • Internal DCI's of NetXMS server changed to UNSUPPORTED
    K Marshall Chen
    Support

    I just upgraded NetXMS server from v2.2.10 to v3.2.400. Everything is fine apart from below DCIs of NetXMS server itself.

    Server.ThreadPool.Load
    Server.ThreadPool.CurrSize
    Server.ThreadPool.LoadAverage
    Server.ThreadPool.Usage
    Server.Heap.Active
    Server.Heap.Allocated
    Server.Heap.Mapped

    it's keeping sending alarm saying the status of DCI changed to UNSUPPORTED. I can't find any post to discuss this case, anyone can give some prompt?


    Image 3.png


  • Can't logon NetXMS Console thru LDAP authentication(Windows AD@Win2008)
    K Marshall Chen
    Support

    @tursiops said in Can't logon NetXMS Console thru LDAP authentication(Windows AD@Win2008):

    Your server is probably configured to be case sensitive in regards to usernames (that's the default).
    The LDAP username is all uppercase, while you're logging in with the name in all lowercase.
    So either use the all caps name to log in, or set the "CaseInsensitiveLoginNames" server configuration option to "1" and restart your NetXMS server service.

    Good catch Tursiops. You are absolutely correct, it's the case sensitive issue. It's no problem by using the id with uppercase. The option 'CaseInsensitvieLoginNames' is the perfect resolution for this issue. Very appreciate your support Tursiops.


  • Can't logon NetXMS Console thru LDAP authentication(Windows AD@Win2008)
    K Marshall Chen
    Support
    1. I configured ldap parameters as attached picture #1, and run ldapsync with debug 4 level, everything goes fine and required users were synchronized from AD correctly.
    2019.04.17 16:14:30.303 *D* LDAPConnection::initLDAP(): Connecting to LDAP server
    2019.04.17 16:14:30.303 *D* LDAPConnection::initLDAP(): servers="xxxxxxx.mydomain.COM:389" port=389 secure=no
    2019.04.17 16:14:30.365 *D* LDAPConnection::fillLists(): Found entry count: 2
    2019.04.17 16:14:30.365 *D* LDAPConnection::fillLists(): Found dn: CN=WANGEW,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com
    2019.04.17 16:14:30.365 *D* LDAPConnection::fillLists(): User added: dn: CN=WANGEW,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com, login name: WANGEW, full name: Wang, Eric W, description: EMPLOYEE
    2019.04.17 16:14:30.365 *D* LDAPConnection::fillLists(): Found dn: CN=CHENMX20,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com
    2019.04.17 16:14:30.365 *D* LDAPConnection::fillLists(): User added: dn: CN=CHENMX20,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com, login name: CHENMX20, full name: Chen, Marshall, description: EMPLOYEE
    2019.04.17 16:14:30.365 *D* LDAPConnection::closeLDAPConnection(): Disconnect form LDAP server
    2019.04.17 16:14:30.365 *D* UpdateLDAPUser(): User added: ID: (null) DN: CN=WANGEW,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com, login name: WANGEW, full name: Wang, Eric W, description: EMPLOYEE
    2019.04.17 16:14:30.365 *D* UpdateLDAPUser(): User added: ID: (null) DN: CN=CHENMX20,OU=Jia Xing,OU=CN,OU=Asia,OU=Users,OU=Global,DC=mydomain,DC=com, login name: CHENMX20, full name: Chen, Marshall, description: EMPLOYEE
    
    1. After that I manually added the LDAP user into local 'Admins' group with all objects access.(pciture 2, 3)

    2. All looks like very good, when I use this LDAP user to logon NetXMS console, it always pop up 'Access Dinied' windows. So I turned on Debug 4 level but unfortunantly there is nothing related the authentication failure.

    2019.04.17 16:17:59.063 *D* [client.session     ] Client session with ID 2 registered
    2019.04.17 16:17:59.063 *D* [client.session.2   ] Read thread started
    2019.04.17 16:17:59.094 *D* [client.session.2   ] Server time zone: CST+08CDT
    

    ===> Anyone who knows something can help me on this? thanks in advance.


    1.png

    2.png

    3.png

    4.png

    5.png

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups