CAS Fields

You should not working on a master branch, the branch should be 6.x-1.0 or 7.x-1.0, Moving from a master to a major version branch.

1. It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
2. Please create a README.txt that follows the guidelines for in-project documentation.
3. Once you've moved your project to a version-specific branch, please run http://ventral.org/pareview and fix any issues found.

Removing review bonus tag, you have not done any manual review, you just posted the output of an automated review tool. Please take an actual look at the source code of the applications.

Thank you for your reviews! When finishing your review comment also set the issue status either to "needs work" (you found some problems with the project) or "reviewed & tested by the community" (you found no flaws).

There are still files other than README.txt in the master branch, make sure to remove them. See also step 5 in http://drupal.org/node/1127732

manual review:

1. "CAS Fields module extends the functionality of CAS module.": so you should specify that dependency in the info file(s).
2. "'access arguments' => array('access administration pages'),": The administration menu callback should probably use "administer site configuration" - which implies the user can change something - rather than "access administration pages" which is about viewing but not changing configurations. Or maybe reuse an adminstrative permission from CAS?
3. "variable_set('fields_that_need_updating_from_cas_server', $form_state['values']['fields']);": all your variables need to prefixed with your module's name to avoid name collisions.
4. cas_fields_client_config_form_submit(): why do you need that function if you use system_settings_form() anyway which will do the same?
5. cas_fields_client_config_form(): why do you use "checkboxes" if there is only one on/off option? You could use "checkbox"?
6. json_decode(): you drupal_json_decode() instead. Same for json_encode().
7. cas_fields_client_user_login(): this is a hook implementation and should be documented as such, see http://drupal.org/node/1354#hookimpl . Same for cas_fields_client_form_alter().
8. _cas_fields_client_add_user_roles(): $save_user is unused.
9. "$form['picture']['#attributes']['disabled']": why can't you use $form['picture']['#disabled'] ?
10. cas_fields.info: that file is not needed, as there is no module with that name.

Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.

Couldn't find any more show stopper issues in the code.
Testing went fine, although I think there might be an issue I didn't test.
In cas_fields_server.module line #32:
You're using regular expressions to get hostname from the referer url without the http://, but the same regex won't work with https (no matches).

This, to me, won't stop the project going full (just an idea that might be good to include, it's supposed to be a centralized login system after all).

manual review:

1. cas_fields_client_config_form_submit(): why do you need that submit callback? system_settings_form() will save the form values for you, you just have to name the form elements the same as the variable names. Then remove that function.
2. "$form["$form_field"]": the quotation marks are useless here?
3. "$form['account']['mail']['#description'] = "This field has been disabled by CAS_Fields_Client module.";": all user facing text should run through t() for translation.
4. You define your own variables, so you should remove them in hook_install(). In both modules.
5. cas_fields_server_cas_server_user_attributes(): is that function a hook? Because it is not documented as such and not called from anywhere.

Although you should definitively fix those issues they are not hard blockers, so ...

Thanks for your contribution, Cristian Andrei! Welcome to the community of project contributors on drupal.org.

I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.

Thanks to the dedicated reviewer(s) as well.