Couple of thoughts

• Can DNN take the place of EBusiness? Just a thought since it looks like you might be duplicating services.
• You can import users into DNN using 3rd party modules. Basically, you would create an XML file out of EBusiness and import them using the module. These modules can import, export, create, update, delete users in DNN. You can update your DNN site weekly (or whatever interval necessary). This scenario would allow you to keep EBusiness as your master data repository and update/sync users in DotNetNuke.

You had mentioned to use 3'rd party modules which could perform the required task, but does DNN synch with ASP

Well, the DotNetNuke framework is built on top of the ASP.NET framework. It is a framework on top of a framework. There is no synching, it is created with ASP. I am having a little trouble understanding EBusiness. I have never worked with the software. It sounds like you are using the EBusiness software as an issue management system. Is that all it does? You could look at doing away with EBusiness and using DNN along with a 3rd party moduel to handle issue management.

As far as integrating the two systems, If Active Directory is used for authentication to EBusiness, then I would set DNN to authenticate with ActiveDirectory. That way users have only one set of credentials to remember. The roles in active directory can be synced with DNN roles. That could be one solution.

The other option is to export the users and their roles from EBusiness and import them into DNN weekly. You would create then have the same users and the same roles. You could even have the usernames and passwords synced between the systems. That could give you one username and password for both systems however, the user would need to authenticate into both systems. The good thing would be that the roles would be in sync between the two systems.

The other solution would be to maybe create a custom DNN authentication provider for authentication against Ebusiness.

Any one else have an idea?