This is the first step in taking a-Expense to Windows Azure.
Highlights of this release are:
- Use of SQL Azure as the backend store for application entities (e.g. expense reports)
- Uses Azure storage for user profile information (the “Reimbursement method” user preference)
- Application no longer queries AD for user attributes needed in the application (Cost Center and employee’s Manager, the expense default approver). These are received as claims in the security token issued by Adatum’s STS.
- Authentication is now claims based.
- Logging and tracing are now done through Windows Azure infrastructure.
Feedback is very welcome!