edpanameno / adweb Goto Github PK

It looks like when the intial is more than 5 characters there is a constraint violation. I should fix this as it's a bug that should not appear!

When you first login to the application, it'll show you the users created during the last 7 days. This is being done by using a view bag ... but somehow this just doesn't look right. Fix this so that it doesn't use the view bag. Maybe try using a partial view to load this data.

I will be creating a Users controller. This will be used to create, view and edit user accounts. The home page of this controller will also give out some basic stats on how many users there are in the domain, and the users that were created in the last 'x' number of days (there should be a default on this value).

Show login count, when the user last changed their password, etc.

When a field that is blank is updated, I am currently showing just a blank. Try to show a more meaningful message such as the word 'blank' so that the user knows exactly what changed from blank to the new field data.

When I select to view users that were updated in the last 'x' days, I am using the field from active directory. This is giving us any user who has had a property updated by either the ADWeb application or by some other application! This means that I am getting users in this list that have just logged on and nothing else has changed. I will have to change the functionality of this so that the application looks at the database for the last updated users (so that we can show what has really been updated thru the app).

Currently I am using a table with two columns that show the details of the user update. There is a nested table in the first column which I just don't like ... this is a ticket to remind me to change this later on!

Can you tell me how this project work? I do not understand MVC and EF in ASP.NET. And can you share database (MSSQL) ?

When creating users in the application, make sure that the fields that are used to display search results for users are created. If one of the fields is empty, the application will fail. I will also have to add some logic when viewing accounts to add some dummy data for those fields that are blank.

When you are editing/updating a user ... trim out the spaces of each of the fields that the user can update/edit for each account.

This is not posting and it's because the field is disabled. Make it a read-only and this should fix the issue.

Though I don't think that this will be an issue ... there should be a check when creating user templates so that you don't have two user templates with the same name which will cause confusion (or so I think).

Just a friendly reminder to implement this. I'll use the EPPlus library to export the users from a group to an excel file.

When creating or updating an OU in the application, there should be a method that can check that it's a valid ou. By valid I mean that the DN of the OU is in the correct format and if it's not then a message should be shown to the user so that they can make the appropriate changes.

When you are doing some background tasks and you want the user to know that something is going on.

When viewing a user, at the top right hand corner the user will see when the account was created. It would be very nice for them to know how long about the account was created (in relation to the current date that is). This way, it'll be easy for the user to start to get an idea on whether or not the user account is a new account, fairly new account or a pretty old account!

It will be very likely that users will be created outside of the application and therefore will not be recorded in the database of the application. There should be a way to scan for newly created users and find those that don't have an entry in the DomainUsers table.

Right now, everyone with an active ad account can login to the application. Use Roles to control who can access the application.

I have created a custom AdvancedFilter to find the list of users that have been changed in the last 'x' number of days. This information will be good to show on the home page of the Users section. At the time of creating this ticket, I have created a custom AdvancedFilter class but I am not getting any results back.

This method returns a ADUser object that is not being disposed of completely. This may be fine for now, but I will need to come back and make sure that this gets fixed.

After you have logged in, the page is not re-directing you to the page you want need to go. Fix this!!

Currently, when viewing all groups in the domain ... I am displaying all groups (including system generated groups that should not show up) and this should be fixed. The reason why I want to remove these users is because I don't want any sort of manipulation to be done one them thru this application (these should only be available to the system admins of the domain).

I currently have the following setup:

ADWeb - Primary Project
ADWeb.Domain - Has models and active directory stuff.

I saw another structure that I like more which would be as follows:

ADWeb.Web - has the files for the web application
ADWeb.Core - models, active directory and infrastructure classes
ADweb.Tests - TDD tests, etc.

The structure above is what I am thinking of renaming the project to, but I have to figure out the best way to do this in Visual Studio (even if it's possible). I am hoping that the refactoring tools in Visual Studio will help me do this.

Use the Quartz library to setup schedules of reports and or jobs in the application. The reports I am thinking of writing consists of generating some stats on the number of users that have been created in the past

When a user is authenticated against ad, the whenChanged property is updated! And since this is what I am using to show the list of users that have been updated this is not good! I should look for a better attribute that I can use to get the date when a user's property(ies) have been updated!

So that when you are displaying them using some of the Html helpers, this doesn't error out. I am currently doing inline checking for this, but it just feels like this is congesting the cshtml code when this should be done at the Model level instead.

When browsing thru the OU's in the domain, the user should be able to see a summary of the number of user objects inside of the OU. The user should also see the number of disabled accounts in the OU as well.

When the basic information of a user is updated, I am checking the values that are posted from the form with the values from active directory of the user. This is causing an issue when I update the user's information and a value that was not changed shows up in the UserUpdateHistory table notes!

Create a table called DomainGroup that will be used to keep track of groups (i.e. when they were created and who they were created by).

The application shows the user id of the user that is logged in, but instead it would be nice for it to display the user's first and last name (or lastname, first format). To do this, I have to store this in the cookie ... find out how to do this and implement it!

When doing a search for users (or any other type of objects in ad), the searches should have a minimum number of characters. I did a search for the letter a, and this caused the application to hang for a while because in my test domain I have about 8,000 users!

This is a value that may be configurable at the application or user level.

When there is a login error message , it should be red. Right now its not and this should be fixed!

When creating user names, check to make sure that they are unique before creating them. I think there is a feature in asp.net mvc that you can use to see if the user name is unique. Also try to think of a way to automatically generate usernames so that if the username you are trying to create is not unique then the user should get a choice of what to use.

The IsAuthenticated calls are not needed in this file as the user will need to be authenticated to be able to access the pages used by this shared template.

When you update a user, the alert box is not showing up correctly.

When viewing a user, and the username has a '.' on it, there is an error message. I will have to figure out a way to fix this. I have looked on the web and they have recommended that I do something to the web.config file but it seems like a bit of a overkill. I may have to change the way that I view users (i.e. pass data to the ViewUser in the from of TempDate or in the ViewBag

When displaying the list of users in a table format (from a search, etc.) show the users who are disabled in a different color ... maybe red or grey to make them stand out.

When using the custom AdvancedSearch Filter object, this is currently returning system users as well (admins, etc.) Need to make sure that these types of accounts are not being returned. I will need to look at creating another filter that will look for accounts that are not Well Known (looks like there is an Enum called WellKnownSidType that I may be able to use for this!!

AD had a field called 'manager' that is used to show who the manager of a user is. Use this to show who the manager of a user is.

This is so that all changes get logged in the database (which I've yet to build at the time of the creation of this issue). I am using this issue as a reminder for me to actually do this!

When viewing members of a group, you might have some groups that have a lot of users ... you may want to (or need to) setup some sort of pagination so that only a few of them can be viewed at one time.

When viewing a user, if I press the enter key this will send an update command to the server. I don't want this and will need to add some checking to make sure that a change has actually been done on the user being viewed.

The quick search currently just uses the display name to search, but this should also search the email, description and other fields that may contain data that can identify the user thru the search being performed.

I am thinking of overriding these two fields so that I can control what shows up when this field is empty for some of the accounts that we'll be encountering.

The role provider will be used for authorizing users of the application. I will need to decide on whether or not I will use a DB to store this information or to use groups in Active directory to control who has access to what features in the application.

I placed the ViewModels in the ADWeb.Domain assembly so that I could be able to pass on one of the ViewModels to the ADDomain class. But it just doesn't feel right that this should be here ... it should be moved back to the ADWeb assembly.

Ticket to remind you to learn about Model Binders in asp.net mvc.

Right now, when you view a user the update button is available even though nothing has changed on the user object. Change this so that the Update button is only available when a change has been made to the User object being viewed.

When viewing a group, currently I am showing only the display name. But I should be also showing the department of the user as well. Come to think about it, I should also be showing the first and last name in separate columns. the reason for this is that the display name cannot be guaranteed that it'll be in the Last name, First name format. Having the information in their own column can also be used to easily sort (by using the jquery table sorter plugin) and make it easier for the user to view the members of the group.