Working on a Geneva prototype has been interesting. The extendability of the framework is awesome, using id management from multiple Security Tokin Services allows for an ease of managing multi-site users with no extra hassle. To understand what I mean, check out the Geneva documentation on the Microsft website, or the MSDN we site.
I would however say that there is somewhere that the framework may be let down. From what I gather, as a basic overview, the STS manages the identity, with the STS of the install, or primary STS, managing all the claims that the Geneva sever passes back to the client. But how does the application update the users details? For an instance using one STS, not a problem, point your appliaction management sections (web-links etc) to management functionallity in the STS. But with more than one STS? How, without making a claim(s) that contains the require data, would the Geneva framework handle that?
From my understanding, there are 2 possible solutions. One is to include the information as part of the claim. This would allow each application to manage the conections between the users and their identity management. The secnd is to use Geneva to send the details to, or show the form of, and have that communicate with the affected STS. How Geneva passed the update through to the STS is up to Geneva, and Geneva could through an exception if it were not possible. Also, the mechanics of the update could be defined at the creation of the trust.
Anyways, I am looking foward to using Geneva. From what I have seen it is a powerful identity platform that will have a great future. Who knows, the theories and practices behind Geneva could become the standard in multi-site identity management.
Friday, June 19, 2009
Monday, June 15, 2009
Understanding
Understanding what you need to do before you start a project is important, but not understanding it all shouldn't stop a project starting. Most project work starts with a phrase like "wouldn't it be cool if we could....." or “I would like to be able to ... so that I can ..." I'll let you fill in the blanks.
This start leads into a review of what exactly is required, how it might work, and what the end user can expect when the project is complete. The more complete the review and requirements list is, the better for the understanding of the people working on the project. However, you can start the project even without this review being complete. I would say that it needs to be 60-70% complete, but at that point the project work can start.
Here is the catch; to start a project where the requirements are not complete invites a risk that you might need to redo parts as the requirements get more and more refined. If you’re willing to take that risk, then there is no problem. Just be prepared to make changes as the requirements change, or when new ones are added.
Why start when you might just need to redo it all? If it is done well, and you are able to mitigate the risk, you can deliver the completed project earlier than if you waited for the entire review to be completed. The risk could mean that it takes longer as you are always redoing the work to fit the latest requirements.
Tuesday, June 9, 2009
Direction
Direction is very important. It is one half of velocity, is a part of vision, and can help you work out where you are. In a project situation, the direction the project takes starts at the very start of the project.
What happens when you don't have direction? There is no purpose, so why continue. There is no confidance that your doing the right thing, so why bother. Without direction you don't know where your headed. You don't know if your using the best tools to get the job done right, first time.
With direction, on the other hand, you can make decisions that are going to get you in the general vicinity of where you want to be. You can plan what needs to be done before you do it, not react to changing tides of what people want.
However, there is one important thing about direction. (Well, probably more than one, but this one is up there.) You can't just start moving in any direction. You need to know where you are headed, atleast generally speaking, so that the direction you take helps you get to where you want to go. Otherwise the gain you have in moving becomes a liability, and can get you into as much trouble as doing nothing at all.
Direction by itself is not good. It needs to be coupled with vision, or what the end goal is. This can be something simple, like a project and a deadline, or more complex like a 5 year plan. But without direction you will just be chasing your tail.
What happens when you don't have direction? There is no purpose, so why continue. There is no confidance that your doing the right thing, so why bother. Without direction you don't know where your headed. You don't know if your using the best tools to get the job done right, first time.
With direction, on the other hand, you can make decisions that are going to get you in the general vicinity of where you want to be. You can plan what needs to be done before you do it, not react to changing tides of what people want.
However, there is one important thing about direction. (Well, probably more than one, but this one is up there.) You can't just start moving in any direction. You need to know where you are headed, atleast generally speaking, so that the direction you take helps you get to where you want to go. Otherwise the gain you have in moving becomes a liability, and can get you into as much trouble as doing nothing at all.
Direction by itself is not good. It needs to be coupled with vision, or what the end goal is. This can be something simple, like a project and a deadline, or more complex like a 5 year plan. But without direction you will just be chasing your tail.
The Beginning
All things have a beginning, and this is my beginning for blogging....Not sure how I will go blogging, or if i will make more than one entry, but lets find out...
Subscribe to:
Posts (Atom)