wiki.getshifting.com

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools

Trace: • Creating a Serverless WebApp with AWS
aixldapedirectory
Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
aixldapedirectory [2025/06/01 11:59] – created - external edit 127.0.0.1aixldapedirectory [2025/07/06 13:10] (current) – [Extend the eDirectory schema] sjoerd
Line 6: Line 6:
 {{tag>aix}} {{tag>aix}}
  
-This is a tutorial on how to setup AIX local authentication through LDAP on eDirectory. The version eDirectory that is being used is 8.8.4 which is installed on a NetWare 6.5 SP8 server. This server is for testing purposes and installed according to this [[netware657|installation report]] but upgraded to SP 8. The AIX version being used is 5.3 TL 6 FP 7 (5300-06-07-0818). This server is also for testing purposes but (because it's a POWER architecture based OS) can't run inside VMware and is running as a LPAR inside the production network. To be able to use the LDAP from the NetWare server I had to use port forwarding inside vmware and add a static route in AIX. \\+This is a tutorial on how to setup AIX local authentication through LDAP on eDirectory. The version eDirectory that is being used is 8.8.4 which is installed on a NetWare 6.5 SP8 server. This server is for testing purposes and installed with NetWare 6.5 SP 8. The AIX version being used is 5.3 TL 6 FP 7 (5300-06-07-0818). This server is also for testing purposes but (because it's a POWER architecture based OS) can't run inside VMware and is running as a LPAR inside the production network. To be able to use the LDAP from the NetWare server I had to use port forwarding inside vmware and add a static route in AIX. \\
  
 > NOTE: During testing I had to change the NetWare test server for a NetWare production server. I found out you need to LUM enable users which is not so easy on a NetWare only environment. In my production environment the schema was already extended with the correct schema. > NOTE: During testing I had to change the NetWare test server for a NetWare production server. I found out you need to LUM enable users which is not so easy on a NetWare only environment. In my production environment the schema was already extended with the correct schema.
 \\ \\
 See [[aixinfo#network|AIX Info]] for more information about static routes on AIX. See [[aixinfo#network|AIX Info]] for more information about static routes on AIX.
-See [[vmwaretips#vmware_server_port_forwarding|VMware Tips]] for more information about port forwarding in VMware Server.+See [[cheatsheet-vmware#vmware_server_port_forwarding|VMware Cheatsheet]] for more information about port forwarding in VMware Server.
 \\ \\
 The steps taken are: The steps taken are:
Line 28: Line 28:
   netware iso name\nw\sys\system\schema\rfc2307-nis.sch   netware iso name\nw\sys\system\schema\rfc2307-nis.sch
   netware iso name\nw\sys\system\schema\rfc2307-usergroup.sch   netware iso name\nw\sys\system\schema\rfc2307-usergroup.sch
-The easiest way to extend the eDirectory schema is by using iManager. If possible, try to use the iManager installed on the local server, when using the portable edition of iManager you could run into [[fiximanagericeerror|this error]]. On NetWare and OES iManager can be accessed (by default) on {{{https://<ip-address>/nps/iManager.html}}}.+The easiest way to extend the eDirectory schema is by using iManager. If possible, try to use the iManager installed on the local server.. On NetWare and OES iManager can be accessed (by default) on {{{https://<ip-address>/nps/iManager.html}}}.
 \\ \\
 After logging in (you'll need admin or equivalent access) expand the schema option and select "Extend Schema". After logging in (you'll need admin or equivalent access) expand the schema option and select "Extend Schema".
aixldapedirectory.1748779162.txt.gz · Last modified: by 127.0.0.1