Commentary

Google Offers Provisioning Toolkit For Enterprises

So you're taking the leap and deploying Google Apps across your enterprise. Rather than add users one by one, Google is giving IT admins a new way to create user accounts: the Apache 2.0 licensed Open Source Google Apps Provisioning Toolkit.

So you're taking the leap and deploying Google Apps across your enterprise. Rather than add users one by one, Google is giving IT admins a new way to create user accounts: the Apache 2.0 licensed Open Source Google Apps Provisioning Toolkit.The toolkit was made available yesterday through the Official Google Enterprise Blog. While there are other options out there for IT admins to take advantage of, those who are fans of Apache or open source tools can use this method instead.

According to Google's Scott McMullen, this toolkit was created for enterprises looking to install hundreds or thousand of users, and specifically targets two scenarios:


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

1. bulk provisioning from user information stored in an existing LDAP, SQL database, or CSV file 2. self-registration, where users input their own info and provision their own account using a Web form

He notes that the Toolkit should run on and Apache, PHP, or Python systems.

After you download the Toolkit and get it configured to your liking, there are a couple of different ways to get users signed up. You can use a Web page that makes it easy for an admin to provision, update, and delete large numbers of user accounts very efficiently. Or, you can set up an authenticated Web page that allows users to self-register. Note that while it can be used to create, update, and delete accounts, it's not designed for unattended sync of user information.

Now there's one less excuse to prevent your business from adopting Google Apps.

The kit can be downloaded here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links