appFabric 1.1 Session Managment losing values - appfabric-cache

I am using appFabric 1.1 with windows 7 for Session Managment but it seems the Caching service is ignoring the Session Time ..
I dont see anything wrong on my web.config
Can someone give me a
allowLocation="true"
allowDefinition="Everywhere"/>

Have you tried following steps in below url? I followed same steps and it is working for me.
https://msdn.microsoft.com/en-us/library/hh361711(v=azure.10).aspx

Related

got forbidden login in on Kie-server

I'm following one tutorial to get kie-drools-workbench and kie-server working: https://www.intertech.com/Blog/simple-setup-of-drools-kie-workbench-and-kie-server-in-one-wildfly-instance/
Installed wildfly and downloaded the kie-server-6.4.0.Final-ee7 and kie-drools-wb-distribution-wars-6.4.0.Final-wildfly8 and move them to C:\apps\wildfly-8.2.1.Final\standalone\deployments
Created user jeff with roles admin and developer on wildfly like the tutorial shows.
on CMD start standalone which starts wildfly 8.2.1
got at C:\apps\wildfly-8.2.1.Final\standalone\deployments
- kie drools .war and .deployed
- kie server 64.0 .war and .deployed
Login with jeff user at administration on http://localhost:8080/ and got redirected to http://localhost:9990/console/App.html#home
Under deployments I have the kie-server and kie-drools enabled, how can I access them?
I can land to the kie Workbench with kie server user at http://localhost:8080/kie-drools-wb-distribution-wars-6.4.0.Final-wildfly8/kie-drools-wb.html but I can't land on the kie-server, got forbidden with user jeff or user kieserver at http://localhost:8080/kie-server-6.4.0.Final-ee7/services/rest/server/containers
I don't find why, I login with jeff user but got forbidden and have to restart all to try another user / pass, like kieserver user.
I access kie-workbench, loggin with kieserver user and under deploy -> rule deployments -> remote servers got the kie server link, but the problem is the same, can't access it. forbidden and only have one shot to get the user pass right, or else I have to restart it.
The objective is to work better with drools rules and debug rules the best way, get to check which fact are loaded and which rules are applied to each fact..
Does anyone got the same issue? Or got something like what I need working?
EDIT: I can work with rules on kie-Drools-wb, the question is, do I really need the kie server to start? Because I only need to create rules based one a database.
I think I found the solution.
I don't need to use the server, the server is wildfly and should be running by then, the drools Workbench as explained on the tutorial works and the demo project is the sandbox.
This is only for academic purposes.

IdentityServer4 & Windows Authentication

I've been chasing this problem around for a while now and I can't get to the bottom of it. I've read the other solutions on here (https://identityserver4.readthedocs.io and https://github.com/IdentityServer/IdentityServer4.Quickstart.UI) and it's still not working, so I've tried to reduce this down to the absolute basics. This is not the actual problem I am facing, but produces the very same outcome. i.e. I can't get Windows Authentication to work.
I clone https://github.com/IdentityServer/IdentityServer4.Samples
I amend Quickstarts/7_JavaScriptClient/src/QuickstartIdentityServer/Quickstart/Account/AccountController.cs so that WindowsAuthenticationEnabled is true
I then goto http://localhost:5000/account/login and attempt to use the Windows external provider and I get 401.
The only difference with this simple sample here, and what I see on my actual system is that I'm getting challenged for credentials on my real site.
Debugging the code I never see if(HttpContext.User is WindowsPrincipal) succeeding, because it's always a ClaimsPrincipal.
Can someone explain to me what I'm doing wrong?
Do you have windows authentication enabled on your IIS site? This needs to be enabled for your WindowsPrincipal to be assigned. Note that windows authentication only works when running behind IIS or IIS Express.

IIS Express doesn't keep session data

I have an application that I run in Visual Studio 2013 under IIS Express server. The problem is that session data is not kept between pages and I find with null objects that weren't null the page before. If I compile the application and deploy it on a web server with IIS it works normally, so it must be something with IIS Express. I searched the config files in the document folders, but really don't know what it is.
Thanks,
Luke
Edit 25/11: I'm debugging the code on the same machine witn VS 2013 and VS 2010 and I found where the code behaves differently. After the code behind has been executed and the page has been built, in VS 2010 the execution ends. In VS 2013 after the page has been built I get another call to the method context_BeginRequest(object sender, EventArgs e), which redirects the application to the starting page, where the instruction Session.Clear() clears the session. The problem now is: why is there this additional call to context_BeginRequest method? Why does it redirect to the starting page and not to the page it is currently in? Thanks, Luke.
I was having a similar problem. My code was running fine on a production server, but when I debugged it on my test machine, the session would be null between saving and redirects.
When I set the session state to cookieless, <sessionState cookieless="true", the session variable would be retained. This was undesireable though because it adds the session name to the url.
Upon further review, I noticed a line in my system.web <httpCookies requireSSL="true" /> When I commented it out, everything worked as usual.
The problem was that my production IIS server was hosting the code using https://, while my test IIS Express server was only using http. So my unsecure cookies were getting discarded.

OpenLdap redirect on write

I am currently trying to setup a redirect on write for an installation of OpenLdap 2.2.
I have two instances running. One is configured to be read-only (only read access, database specified as read-only) and has redirect configured to point to the second instance. The second instance is configured to allow for the desired write permissions.
When I attempt a modify on the first instance it fails as expected but does not send back the referral. Am I missing a piece of the configuration? Am I even on the right path? Any guidance would be greatly appreciated. Thanks.
In the database section of you slapd.conf do you add the redirection like this ? :
updateref "ldap://master-host:port/"
So, it turns out the best way to do this is to go ahead and set up replication using slurpd and point all requests at the slave instance. Unfortunately you can't set up the master and slave on the same host (for obvious reasons, but still), so I had to spin up a second VM to get this going.
Honestly, if I was not trying to replicate a redirect problem it wouldn't be worth it, but I have to duplicate a production issue.
For more information on slapd and specifically slurpd, the OpenLDAP documentation is actually crazy helpful: slurpd config for OpenLDAP 2.2

How do I get more details on my request error on IIS7

I have deployed a REST service on an external server (IIS7). When I start the service from VS on the Dev server it works fine. But on the server i get:
Request Error, The server encountered an error processing the request. Please see the service help page for constructing valid requests to the service.
How do I get more details on this error? I have looked in the log files directory that is configured under Logging feature for this web site in IIS Manager, but there are no files at all for this site it seems.
You should look in the Windows Event Log using the Event Viewer application (eventvwr.exe). Output to the IIS log files may be buffered so their contents may be updated after a restart, or when IIS is set to do it. Restarting IIS is a surefire way to force this.
Here is a blog post on how to do this.
I'm aware of 3 ways to get nicer errors:
Set UseVerboseErrors in InitializeService method. However, this won't give you anything if your error occurs before InitializeService is called (which happens).
Set IncludeExceptionDetailInFaults to true using an attribute before your service class.
Set IncludeExceptionDetailInFaults to true using web.config.