I have set up a login using our Common Security Platform, by making a Login Page and adding a custom Module to that page that handles the login. When creating a Child Portal this page/Module is created with the new child. But when I create a Parent Portal - this page isn't created and the module with it. So I'm left unable to log into the new Parent Portal that I have just created. Does anyone know why this would be happening? Or if there is a way to - since it isn't working currently - to add this page/module without having to be already logged into the parent portal?

I can't log in - so I can't add the page/module. So I need a way to add it through the code or database? Any help would be much appreciated.

Is the Common Security Platform a DotNetNuke portal?

When you add a parent portal, which skin is assigned to the portal? Can you visit the portal's home page? If you can, can you visit http://ParentPortal.com/Login.aspx? That is the "default" login for the portal. If the parent portal is using a standard skin, it also should have a login link on it. But, you should be able to get to the login page directly using the link I described.

Common Security Platform is a website our company uses to authenticate users. Essentially I made a Module that when the Login.aspx page loads it send the users to the Common Security Platform, then once they are authenticated they are redirected back to the site. But since I have changed the authentication of the DNN Portal to use this Common Security Platform, when I create a Parent Portal and the Login.aspx page isn't added to the new portal. When I go to that Parent Portal - I get an error, instead of any type of Authentication.

I think I need a few more details. (Forgive my asking some basic questions, but I need to understand what's happening.)

1. You have created a new Authentication Provider, correct?
2. Have you installed it?
3. Have you enabled it?
4. Have you enabled it for your new portal?

5. You say that there is an error. Can you provided details of the error? Is there detailed error information written into the site's Event Log?

6. Are you able to debug the Authentication Provider? (A typical way to do this would be to attach the VS debugger to the DotNetNuke process, and then you should be able to set breakpoints in the code to see exactly what is going wrong and where.)


The more details you can provide, the more likely I will be able to help.