Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 10 months ago.
Improve this question
I have Windows 10 and I want to run IIS.
I have activeted all features for it, as you can see here.
Then I type "localhost" in the browser and I take
"HTTP Error 503. The service is unavailable."
In some forums they say to control the log HTTP Error file, so I do, but it is empty.
Then I go to the ISS manager to see for configurations.
How can I resolve this "Il server è configurato per l'uso dell'autenticazione pass-through con un account predefinito per accedere al percorso fisico specificato. Tuttavia, Gestione IIS non può verificare se l'account predefinito ha l'accesso. Verificare che l'identità del pool di applicazioni abbia l'accesso in lettura al percorso fisico. Se questo server è aggiunto a un dominio e l'identità del pool di applicazioni è NetworkService o LocalSystem, verificare che '< dominio>\< nome_computer>$' abbia l'accesso in lettura al percorso fisico, quindi riprovare queste impostazioni."?
I understand that I have to verify if the identity of the App pool has the reading access to the physical path. Please help me. Thank you.
With IIS, the error message "HTTP Error 503. The service is unavailable." typically means the site itself is running but the application pool associated with the site is stopped. Check the application pool and start it if is stopped.
If you see the application pool stopping again after you request the page, check your Event Viewer for error entries explaining why it stopped the pool.
Just update the credentials in Application pool. You can update this by going to IIS manager=>Application Pools=> your pool name=>Right click then Advance Settings =>Identity=> custom and update the username and password that may help.
Related
hello guys
i run my asp application in server and check this security test with acunetix
my application has 1 high security bug ("long password denial of service")
i try some solution to fix it :
-add asp validator with 15 character limitation
-check password length with java script
-check password length on server side
-put an captcha on my login page
But had no effect and still gives an error "long password denial of service"
whats wrong!?
Do you think that acunetix mad
Problem Solved!!!
iis not install full option , server manager says i checked all option and istall all iis features ,
then i test it again and problem solved
I've encountered a challenge regarding internet-facing deployment installation for CRM using a AD FS server. After the setup is complete, users are able to access the CRM server - but when trying to run custom pages the following error message is prompted:
"The authentication endpoint Kerberos was not found on the configured Secure Token Service!"
I've found several solutions on the internet for this issue:
First I found a KB article from Microsoft providing a possible
solution, this involves updating MEX endpoints by running a provided
PowerShell script.
(https://support.microsoft.com/en-us/help/2828015/configuring-ad-fs-2.1-with-microsoft-dynamics-crm-2011).
But this doesn't seem to be the issue.
Another solution could be to update the CRM rollup version (currently have version 14 installed, latest is version 18) - this is something that I want to avoid as it might lead to further issues.
Have anybody else encountered a similar issue, and in that case how did you solve it?
I have just spent last few days to figure this exact same error message and it turned out that it was the "Domain" attribute in crm connection string. Copied my answer to my own question at the Microsoft Dynamics CRM community forum here:
"Well, I found the culprit - it was the Domain attribute in the connection string:
For connecting from outside the domain, it does not like to have a Domain in the connection string:
Connection string format 1 (without Domain attribute): "Authentication Type=Passport;Server=https://devcrm.myco.com;Username=devuser#myco.com;Password=pwd" - this works both inside and outside the domain "myco.com"
Connection string format 2 (with Domain attribute): "Authentication Type=Passport;Server=https://devcrm.myco.com;Domain=myco;Username=devuser#myco.com;Password=pwd" - this only works inside the domain myco.com but NOT outside (exception: The authentication endpoint Kerberos was not found on the configured Secure Token Service!)
The key is in the Xrm.Client.CrmConnection.ClientCredential:
If Domain is NOT specified in the connection string, when connecting from outside domain, Xrm.Client.CrmConnection.ClientCredentials.UserName is populated whereas the ClientCredentials.Windows.ClientCredentials.UserName is empty.
But if the Domain is specified, Xrm.Client.CrmConnection.ClientCredentials.UserName becomes null and Xrm.Client.CrmConnection.ClientCredentials.Windows.ClientCredentials.UserName populated, which led to the service trying to authenticate user as a Windows AD user so of course it would fail when running app from outside Windows domain. And it explains why the same app works inside the domain even with Domain specified in the connection string.
For more detail, refer here for my original post asking for help in Dynamics CRM Forum
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I installed SDL Tridion 2011 SP1 on my windows server 2003 R2. When I am trying to access it in browser it is throwing below error -
Error- 1(Case -1) When I get logged in through my account(abc)
if I try to create a new user i get below error -
The remote server returned an error: (401) Unauthorized.
Below is the detail of error -
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.
Error -2 (Case-2) When I try to do any adminisatrative activity through MTS user
any administrative activity such as to create new user etc through below error -
Invalid URI: cme:accmng.
Below is the detail of error -
Invalid URI: cme:accmng.Unable to get TOM object for URI: cme:accmngUtilitiesTDS.GetNativeURITDSE.GetObject
Could anybody give me a right direction to get it work?
Edit- below is the Below is screenshot of HTTP traffic using Fiddler tool –
Edit-2
I am Completely unable to access anything in the administrative panel see the below screenshot for same
below are the detail for few admin activities --
(a) Show User/Show Groups/Open Access management–
Error- Invalid URI: cme:accmng.
Detail of error is as below --
(80040325) Invalid URI: cme:accmng.
Unable to get TOM object for URI: cme:accmng
UtilitiesTDS.GetNativeURI
TDSE.GetObject
(b)-Show Protocol Schema/ Show Publication Target/ Open Publishing Management
Error -Invalid URI: cme:publmng.
Detail of error is as below --
(80040325) Invalid URI: cme:publmng.
Unable to get TOM object for URI: cme:publmng
UtilitiesTDS.GetNativeURI
TDSE.GetObject
(c)-Show Multimedia Types
Error- Invalid URI: cme:mmtypes
Detail of error is as below --
(80040325) Invalid URI: cme:mmtypes.
Unable to get TOM object for URI: cme:mmtypes
UtilitiesTDS.GetNativeURI
TDSE.GetObject
So , "Invalid URI:....." error respective to various type of admin activity means ,This user do not have any admin right.
Even when i try to create an publication in Content management panel, i am getting any such option in context menu . see the screenshot below --
Note:- These all ctivities in this Edit are performed through the MTS user.
Each 401 error in your Fiddler log is eventually followed by a 200 OK response, this is unfortunately a result of the HTTP NTLM authentication scheme. In short, your browser doesn't know that it needs to authenticate at all until it gets bounced with a 401 response containing a WWW-Authenticate response header. So from that point of view all is expected and appears to be working.
In both cases you seem to mention it fails when creating a new user, are there other actions which result in an error too? If not, then I would focus on the addition of a new user, which might indicate that your MTSUser account (or the identity under which the Tridion Content Manager COM+ application is running) is unable to browse your domain perhaps?
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have a postfix mail server on ubuntu on my virtualbox,now the domain of the mail server is abc.com...hence it receives mail from any "from address" but the "to address" needs to be proper i.e a valid user in the mailserver.
Now,in my project i am sending fake mails to user whose mail id consists of other domains too...like cde.com
My final objective is to show the mails in the mail server.
When i tried that ,it goes directly in to the mailserveer logs i.e /var/log/mail.log i.e as an error
is there any way i can store these mails in the mailserver??
You want not only a Catch-All configuration like accepting any mail to *#abc.com but also to have a Catch-Anything configuration to accept any mail to *#* ?
This is possible if you have the PCRE support compiled into Postfix. Then you need virtual users in your configuration (see the Posfix documentation) and tweak it as follows:
Make sure that your Postfix is already configured to accept mail for at least one user and one domain. And that this is tested.
1) In main.conf set
virtual_alias_domains =
virtual_alias_maps = hash:/etc/postfix/virtual_forwardings, pcre:/etc/postfix/virtual_forwardings.pcre
virtual_mailbox_domains = hash:/etc/postfix/virtual_domains, pcre:/etc/postfix/virtual_domains.pcre
The hash: parts are the known from the docs. And the pcre: parts are new.
The hash: parts can also be omitted.
2) Create the file virtual_domains.pcre with the following content:
/^.*/ OK
This accepts any domain as valid recipient domain.
3) Create the file virtual_forwardings.pcre with the following content:
/#.*/ someuser#example.com
This forwards any local part of any domain to the Postfix user someuser#example.com. Make sure that this is a valid virtual or local user.
In this configuration it seems that Postfix is an Open Relay, but it does not relay for other domains. It accepts mails for any domain and locally delivers the mail to one mailbox.
Sometimes you will then notice a log entry telling you something like "don't list abc.com in mydestination and virtual config". This warning can be ignored as this "strange" setup is not usual.
FTR:
An alternative way to do it by sending any mail to "some.local.user" (a shell user)
Required: postfix-pcre package
in main.cf
luser_relay = some.local.user
local_recipient_maps =
virtual_alias_maps = pcre:/etc/postfix/virtual_alias.pcre
mydestination = $myhostname, pcre:/etc/postfix/mydestination.pcre
File: /etc/postfix/virtual_alias.pcre
(catchall mapped to "some.local.user")
/\/#/ some.local.user
__
File: /etc/postfix/mydestination.pcre (we accept whatever you throw at us)
/.*/ OK
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I want to develop a website in ASP classic that uses HTTP Authentication against a database or password list that is under the control of the script. Ideally, the solution should involve no components or IIS settings as the script should be runnable in a hosted environment.
Any clues/code deeply appreciated.
It is possible to do HTTP Basic Authentication in pure classic ASP VBScript.
You will need something to decode base 64. Here is a pure VBScript implementation. You will also need to make sure that in your IIS config you turn off "Basic authentication" and "Integrated Windows authentication" as these will interfere with what you get back in the HTTP_AUTHORIZATION header.
Here is a sample implementation that just echoes back the user name and password.
<%#LANGUAGE="VBSCRIPT"%>
<!--#include file="decbase64.asp" -->
<%
Sub Unauth()
Call Response.AddHeader("WWW-Authenticate", "Basic realm=""SomethingGoesHere""")
Response.Status = "401 Unauthorized"
Call Response.End()
End Sub
Dim strAuth
strAuth = Request.ServerVariables("HTTP_AUTHORIZATION")
If IsNull(strAuth) Or IsEmpty(strAuth) Or strAuth = "" Then
Call Unauth
Else
%>
<html>
<body>
<%
Dim aParts, aCredentials, strType, strBase64, strPlain, strUser, strPassword
aParts = Split(strAuth, " ")
If aParts(0) <> "Basic" Then
Call Unauth
End If
strPlain = Base64Decode(aParts(1))
aCredentials = Split(strPlain, ":")
%>
<%= Server.HTMLEncode(aCredentials(0) & " - " & aCredentials(1)) %>
</body>
</html>
<%
End If
%>
Hooking the user name and password up to something meaningful is left as an exercise for the reader.
By definition, HTTP Authentication is something that is requested by the WebServer, I doubt you will find a solution that does not result in no IIS Settings being applied.
The web browser will connect to your web site, and unless your server responds with an HTTP response code HTTP/1.1 401 Unauthorized, the browse will not pass through the credentials.
You could try and force a response code of 401 and set the header
WWW-Authenticate: Basic realm="SomethingGoesHere"
Then the browser will prompt the user for username and password, but will be sent over clear-text to the browser (base64 encoded), like this:
Authorization: Basic YnJpYW5iOmJvYmJ5Ym95
Which is translated from Base64 to:
brianb:bobbyboy
I don't know if you'll have access to the Authorization header from your ASP page, or if the Web Server is going to freak out because someone is trying to pass credentials to it when its not expecting it, but could be worth a try...
Hi are you trying to get a list of users from a database or use network based permissions on the HTTP server?
If you are using a database use ODBC and DSN
Dim DatabaseObject1
Set DatabaseObject1 = Server.CreateObject("ADODB.Connection")
DatabaseObject1.Open("DSN=DSNname;")
If you are wanting a password dialogue box (from the server), you will need to alter IIS settings for a good guide to this..
http://www.authenticationtutorial.com/tutorial/