Solved

Exchange 2013 - Forms based authentication

Posted on 2015-02-16
7
101 Views
Last Modified: 2015-03-05
Hello!

We have a small DAG with 3 member servers and one witness servers. Some time ago our forms-based authentication stopped working and we had to move back to basic authentication to allow for OWA to work. This works fine, but we would like to get the "pretty login page" back online.

We had a case open with Microsoft, requesting numerous traces/logs but so far we had no luck figuring out the issue. We have been trying different IIS settings as well. The only thing that was done at some point before the issue started was new certificates were applied to our servers.

We did also apply a CU7, which I assume re-installs the whole Exchange pretty much, but it did not clear the issue.

What we are seeing while the forms-based authentication enabled is the inability to log in. Putting the credentials in and hitting the Enter key re-loads the page and we are back to the login screen. Putting incorrect credentials works - the error stating that username/password is incorrect is properly generated.    


Thanks!
0
Comment
Question by:rr2r
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
7 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40612671
Seen this a couple of times. Sometimes entering a wrong password allows you to enter the correct one and get logged in.

Which authentication method are you using within FBA? Have you tried changing them at all?
Anything odd about the usernames? I seem to have the most problems when there are odd characters involved. Had one site that gave huge grief because the login was an employee number "#1234" - Exchange did not like that one bit.

Simon.
0
 
LVL 1

Author Comment

by:rr2r
ID: 40612773
We are pretty sure that it does not work for anyone - most of our facility are production folks who use OWA and we had numerous users report this behavior. We have been changing the authentication methods around, yes. Right now the one we are using is "basic". The default before was "forms based authentication".  Here is what works:

what-works.JPG
...and here is what we would like to work (but currently does not):

what-we-want.JPG
Perhaps we are not setting this up properly, in case one authentication method requires or collides with another... ?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40612978
That wasn't what I was expecting.
When you enable FBA you three authentication options - domain/username, UPN or username only (with a default domain specified). Have you tried all three options.

Have you reset the virtual directories at all? If not, I would reset them back to the default.
Then test again without making any changes to the configuration.
If that then works, switch to FBA with domain\username as the first option. Remember to iisreset after making the change.

Unusual for a problem like this to continue after installation of the Cumulative Update.

If it still fails, I would have to start looking at IIS being the possible cause.

Simon.
0
Office 365 Advanced Training for Admins

Special Offer:  Buy 1 course, get 2nd free!  Buy the 'Managing Office 365 Identities & Requirements' course w/ Accelerated TestPrep, and automatically receive the 'Enabling Office 365 Services' course FREE!

 
LVL 1

Author Comment

by:rr2r
ID: 40613098
Yes, the virtual directory was recreated as one of the steps with went over with MS. They also collected IIS logs as well. Waiting now for their 2nd level support to make contact with us...
0
 
LVL 1

Author Comment

by:rr2r
ID: 40615855
@all

I will not be able to work on this till Monday.... Thanks!
0
 
LVL 1

Accepted Solution

by:
rr2r earned 0 total points
ID: 40637288
The final resolution, which we worked toward with Microsoft was to actually acquire a new certificate and apply that. Something was off with the one that we received the first time OR it was not applied properly the first time. According to Microsoft the SSL "handshake" was not working properly and so the secure connection was not being opened after the login info was provided by the user.
0
 
LVL 1

Author Closing Comment

by:rr2r
ID: 40646474
Solution was provided outside of these forums.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…

742 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question