Update Needed
This page needs to be updated
These files should allow you to configure an LDAP server to store SOWN user details. The schema and configuration should be update along with the website to be working soon. The RADIUS server needs to authenticate with the LDAP server, this should work for the VPN but probably not with 802.1x yet.
For those who have not used LDAP before schemas are files which define the objects that can be added to a LDAP server and the variables which can be contained in those files. Each variable and object must have a globally unique OID and name. The OIDs used are the same as those used in SNMP. To create a sub field in an OID simply a a period (.) and then a new number. For example ECS has the OID 1.3.6.1.4.1.12285 assigned to it by IANA, to add a new sub assignment for SOWN we add .486 so SOWN's OID becomes 1.3.6.1.4.1.12285.486. To keep things separate a further number has been added to specify the OID is for the LDAP server. This meens that the OIDs which describe the objects in the LDAP server all begin 1.3.6.1.4.1.12285.486.1. Don't worry if you don't understand this all you need to know is that any object entered into the SOWN custom schema should have the numbers 1.3.6.1.4.1.12285.486.1 before it like the current ones and no two numbers should be the same.
The custom schema omniFi.schema currently allows you to create two new objects SOWN users and SOWN nodes. It is probably necessary to update the schema to do everything we need it to do.
To uniquely identify objects of its type it uses the OID assigned to ECS with the suffix 486.1 forming an OID of 1.3.6.1.4.1.12285.486.1.* The names of the fields are prefixed with netOmniFi to avoid collisions with other names.