I have a SharePoint 2010 site that is configured for Forms Based Auth using custom role, membership and profile providers. This works perfectly using the OOTB SharePoint 2010 FBA form (ie. under /_forms in the web app virtual directory).
My problem is with a custom login form that is located in a separate folder, /Landing/Login/default.aspx. I've configured the web app to point to this form (contains an unmodified ASP.NET login control), which is rendered when the user hits the root URL. The problem comes when they submit their credentials and the form posts back for the redirection to /_layouts/Authenticate.aspx. It stops cold with a 403.
If I revert back to the OOTB FBA form (using the same providers) everything works fine. Any suggestions on what could be going wrong?
So, I discovered the solution after examining the OOTB FBA login form that inherits from Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage and taking a look at the code with Reflector.
I modified my custom form to inherit from the same object and replicated the content placeholders (some I put into a panel control with the visibility set to false) from the OOTB Form.
Presto. My custom form now authenticates flawlessly. On reflection, this seems an obvious thing to do, just isn't documented anywhere.
I just went through this process myself, and wrote up the steps I had to take to get FBA working with a custom login form. Hopefully it'll help the next poor soul that is trying to get this to work.
http://mikevallotton.wordpress.com/2010/10/18/sharepoint-2010-claims-authentication-custom-login-form-2/
If you want to use ready-made solutions for the management of FBA users, you should take a look here:
http://www.devit.eu/products/121-fba-manager-sp2010-forms-based-authentication.aspx
Related
I am a bit confused about what I've implemented so far should or should not work. (I've also read the official docs but I am not sure how up to date is, things are changing week by week)
Context
I am implementing a web site where I utilize AD B2C for authentication. (using out of the box ASP.NET Core 3 template) All works except KMSI.
I've created the User flows (policies) as the pictures show (see below) The KMSI checkbox is there, but no effect.
Question
What am I missing? Should this work out of the box, or should I upload a custom policy XML, if yes then why is the KMSI checkbox in this built in template, using the configured userflow?
What I've done so far
At the moment Keep me sign in is not supported in basic user flows. Please use Page Layout Version 1.0.0 for Unified sign up or sign in page, so the KMSI check box will not appear.
I have a SharePoint 2010 web application migrated to SharePoint 2013. this is a classic mode web application, we are not using claims, my client doesn't wants it ( Don't ask why?).
I had other web application migrated as same process but i can add users in them.
but in this i am not able to.
I can add users and find users in the web application in central administration. But not in the web application itself.
I am not sure what changes i have to make so that it starts picking or finding users from the people picker. any ideas.
it was because of the asp.netvalidation=2.0 not present in the httprequest line in webconfig. there was no validation for the input provided in any input box.
once we added the asp.net validation it worked fine.
It is a browser compatible issue as well whereas in new browser like IE 10 and other latest browsers it doesn't play well.
we updated the
In short the fix is to edit the pickerdialog.master file in notepad and add a meta data tag, , to the header section.
well keep in mind always save a local copy of your original master page.
it is recommended not to update any original files, we can run the site in compatible mode too.
We have an existing live MVC 4 website that works exactly as it supposed to, running in an Azure Web Role.
A third party want to embed our site in an iFrame on their site (a small part of it anyway, one form really)
I'm no fan of iFrames but this is what they want to do and our business are happy for them to do it.
Except it doesn't seem to work at all.
So I tested it myself with an html page just running on my machine.=, with just an iFrame and a link to the site.
The default page loads fine. It is a forms login screen, when I submit a login, the site crashes into the exception handing and it doesn't provide much useful information.
I then tried pointing the iFrame at the site running in my dev environment. Submitting the login and debugging into the action, the code flows through correctly, no error and tries to return the correct view, but iframe refreshes to the login screen again.
What could be causing this? What am I missing?
I have a webpart, and I insert that webpart into a site of Sharepoint 2010 (WSS).
I save a site as template by that site. After, I create a new site with that site template. I export this site, and after I import it. I see a error in import site:
"A Web Part with this ID has already been added to this page".
Please help me to fix it.
(It work well on MOSS 2010)
Is new site is on the same farm as the originating site?, I would also asume that this is a Team site with Publishing features or a publishing site al togethere right?, if so, basically is having a conflict of GUIDS for a particular web part within a page or layout. If you see most of the site comming up, then is easier, because you could open the page or layout using SPDesigner and change the guids of the added webparts on the page; if not, you might need to crack open the template file and do it there.
Changing the GUIDS might help you to bring the page up, however any change done of the front-end could reverse the changes, so the best option is to edit the page and re-add the web parts, so it takes a new GUID for good.
How to login to windows authenticated sharepoint site automatically without prompting for credentials using VB.net. any help would be appreciated.
Thanks in advance.
Info you've given us is not enough to answer corretly; I hope this helps:
If it's a custom solution that is in the sharepoint; sharepoint should do this automatically if the user has the appropriate read permissions given in the "User permissions" of the site and there should be a ie trick like:
Go to Internet Explorer options.
Add the SharePoint site to the Trusted Location.
Go to Custom Level and scroll to last option and change it Automatic logon with current username and password.
You may also do it for Intranet Zone if required.
reference here
Like you can understand, it's a client based decision as well, so there should be no fully-operable way to do this.