I am trying to use FormsAuthenticationConfiguration to set my LoginUrl at runtime in my app.  I am testing it as follows

GLOBAL.ASAX 

	Protected Sub Application_BeginRequest(ByVal sender As Object, ByVal e As System.EventArgs)

		' Set the LoginUrl.
		Dim instance As New FormsAuthenticationConfiguration
		instance.LoginUrl = "MyNewLogin.aspx"

	End Sub

    Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
        Dim currentLoginUrl As String = FormsAuthentication.LoginUrl
        Response.Write(currentLoginUrl)
    End Sub

 in my Default.aspx.vb page.

The problem is that it is writing out "login.aspx" on the page...

Does anyone know what I am doing wrong?

oh how quickly one's post can get bumped to the bottom of the page.

 So you need to change the Login page temporarly ?

Actually your code doesn't work because you are just creating an instance from the FormsAuthenticationConfiguration class and it will not be linked to the actual configuration.

Also you can't use the FormsAuthentication.LoginUrl  because it's read only.What are you trying to do ?

Are you using a different login page for each role ?

I am in the process of building a content management system.  There is already a Login.aspx page but it is branded with the CMS stuff.  The goal is to also build a login module that the client can use to override my login page with their own theme.

Select [ID] from [Pages] where [Module] = 'Login'

if it exists {change the login page}

 Ok,

What about keeping your login.aspx page , and in it's page_load method, you check that database table and decide if you need to redirect to the login page that you want.

Yes, this is definately possible, though I would prefer not making extra trips... I just thought that the FormsAuthenticationConfiguration would work...

also, i think a server.trasfer would work better than a redirect.

rockinthesixstring:

also, i think a server.trasfer would work better than a redirect.

Sure, But it will keep the Login page title.But in your case yes it's better.

You can also Handle the AuthenticateRequest event in global.asx file and check your client paged and redirect to whatever paeg you want.