teaminsight-legacy / ad-schema

A gem that models active directory's schema and provides a friendlier interface for reading and modifying data.

AD::Schema

A gem that models active directory's schema and provides a friendlier interface for reading and modifying data.

Description

AD::Schema is an implementation of the ActiveDirectory schema in ruby. It uses AD::Framework for all the base concepts and simply defines the attribute types (syntaxes), attributes and object classes (abstract, structural and auxiliary).

Installation

gem install ad-schema

License

Copyright (c) 2011 Collin Redding, Matt McPherson and Team Insight

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

ad-schema's Issues

Implement timestamp attribute type

Some dates in AD are stored as a strange timestamp similar to the unix timestamp but from a different starting point. See:

http://msdn.microsoft.com/en-us/library/ms676823(v=vs.85).aspx

We need to convert back and forth to this number with a timestamp attribute type.

Add integration tests with open ldap

Like ad-framework. Would be a good time to write documentation for the ldap server.

Implement bit string attribute type

For security principal object_sid and sid_history

Clean off the ActiveDirectory module

The ActiveDirectory module has a bunch of old code defined on it. For now this module should be blank. The requires are also bad.

Merge attribute types with reorg ad-schema

Merge all the new attribute types with the reorg to ad-schema. There may even be some merging between ad-framework and the new attribute types stuff.

Update attribute types to use ad-framework

They should inherit from ad-framework's attribute type and override any methods as necessary. Also see: https://github.com/teaminsight/ad-framework/blob/master/test/support/attribute_types.rb for how to register the attribute types.

Implement unicode password attribute type

There's a pattern for converting a password string to a valid unicode string. Talk to me when were ready to do this one.

Implement Integer attribute type

Very similar to string attribute type, just have convert to integer and back to string. Make sure any attributes listed with this are actually stored as integer values and not float values.

Move structural_classes out of folder

I'd like for all the structural classes to not be defined in a folder and instead directly under the active_directory folder.

Implement dn_array attribute type

This is slightly different in that it needs to define multiple arrays for the dn's and the entries.

Write a base README

ad-schema looks super ghetto without a README

Implement generalized time attribute type

AD stores some timestamps as a 'generalized time' string that is a timestamp in ISO 8601 form. This needs to be able to go from a string to a time object and back.

Implement DN attribute type

A DN is essentially a foreign key to another object in AD. This should behave similarly and allow you to access both the DN and the associated object. Something similar to has_one or belongs_to in rails.

Implement Auxiliary Class pattern

Auxiliary classes in AD will essentially work as included modules but need to apply attributes, validations and other behavior in a common way to the model.

ActiveDirectory::User has multiple of these (PosixAccount, MailRecipient, etc...) and is a good starting place for developing this.

Testing

Bring in assert, setup the LDAP connection stuff like ad-framework and we need to start testing the classes.

Define auxiliary classes for User

User has a lot of auxiliary classes that complete its functionality. Once ad-framework supports these, we need to define them.

Flags attribute type needs a custom inspect

Make it happen

Boolean attribute type

Is not like the others and it should be.

Update structural classes

The structural classes need to use the new ad-framework stuff as needed. See: https://github.com/teaminsight/ad-framework/blob/master/test/support/structural_class.rb for how to define structural classes.

Attribute type timestamp special values handling

Timestamps can have a special value of 0 or 0x7FFFFFFFFFFFFFFF that basically mean this value is not set:

http://msdn.microsoft.com/en-us/library/ms675098(v=VS.85).aspx

Let's have this attribute return a nil when a timestamp is 0 or that stupidly large value.

Update dn attribute type

It should do some extra magic with looking up objects for you. Some of this may require more searchable features from ad-framework.

Implement flags user account control

There is already a flags attribute type but it needs specifics defined for the user account control attribute on a user. This should be done similarly to the system flags attribute that has already been implemented.