Is it possible to enable RDS for ColdFusion 8 on a server that requires Basic Authentication? The web server is IIS.
RDS is it's own protocol and from memory has nothing to do with IIS. The authentication for RDS is managed during the initial set up/install. You can change the password using the ColdFusion administrator.
Another gotcha is that even though you enabled it during installation it sometimes remains disabled. So you need to edit the web.xml file (make a backup first). Here's a link to a kb article with detailed instructions: http://kb2.adobe.com/cps/172/tn_17276.html
Hope this helps.
Related
I'm new to AWS and I got a Spring microservice project that serve in AWS. I have Jboss7 running in AWS-EC2 instances and having setup AWS-ELB for load balancing.
I encounter an issue to remove microsoftsharepointteamservices version number in response header from a URL, for example www.domainName.com/_vti_bin/shtml.exe.
However, i have not idea why microsoft share point service come into picture as I do not install any web server or apache httpd in AWS.
Why shtml.exe is accessible in default AWS setup? Or is it the other issue that related to ISS?
Please kindly advice. Thank you so much.
I found the root cause for this issue. This is due to we have setup Liferay CMS system in our AWS. And Microsoft Share Point service team service is bundle together with Liferay by default to support for Content Search module.
I have a provider hosted app (a normal asp.net web forms application) deployed on a typical web server IIS 7.5.
While launching the app from SharePoint Site in Office 365 Multi Tenant, it's throwing the below issue on App launch.
On capturing details using Fiddler, found the following when the app is launched
SPAppToken=&SPSiteUrl=https%3A%2F%2Fabc.sharepoint.com%2Fsites%2Fspdev%2Famsdev%2Famitamsdev&SPSiteTitle=amitamsdev&SPSiteLogoUrl=%2Fsites%2Fspdev%2FSiteAssets%2Flogo.gif&SPSiteLanguage=en-US&SPSiteCulture=en-US&SPRedirectMessage=EndpointAuthorityMatches&SPCorrelationId=31477a9c-2902-204a-8393-67eced1a10b8&SPErrorCorrelationId=31477a9c-2902-204a-8393-67eced1a10b8&
SPErrorInfo=The+requested+operation+requires+an+HTTPS+%28SSL%29+channel.++Ensure+that+the+target+endpoint+address+supports+SSL+and+try+again.++Target+endpoint+address
The SPErrorInfo Part is interesting. I am unable to confirm whether we really need the remote site to be configured for https?
Additional Information - Identity Provider is ACS and it is a low trust app.
Can someone suggest?
Regards,
Nitin Rastogi
In a production environment, you should always be using HTTPS. If you don't, you're exposing yourself (and your organization) to many risks.
If this is your development environment and you are confident this isn't an issue, you may want to look at the accepted answer to this question on the MSDN forums, which mentions the same error message. Their solution to bypass the HTTPS checking:
$c = Get-SPSecurityTokenServiceConfig
$c.AllowMetadataOverHttp = $true
$c.AllowOAuthOverHttp=$true
$c.Update()
When packaging the SharePoint App from Visual Studio, you must ensure that the URL you use is using HTTPS:
In IIS, add an HTTPS binding to the site to achieve this. You would have to reupload the App to SharePoint after packaging it with the new HTTPS URL.
More information here.
I have a hypothetical request to pull in 3 data fields into an orchestration but only via a web service.
how can I do this with biztalk?
thanks
As #Tim has mentioned, the WCF Publishing Wizard is a good starting point.
Overview:
http://msdn.microsoft.com/en-us/library/bb226350
More here : http://msdn.microsoft.com/en-us/library/bb226564.aspx
A couple of notes:
You'll need to build and deploy your BTS project to a dev environment before you publish.
Make sure that when you publish you deploy to an app pool with the same user as the BizTalk Isolated host.
You don't actually need IIS / WAS to host the service - Biztalk can self host with e.g. WCF-Custom. So you can avoid the Isolated host in your production environment and turn off IIS entirely. This has performance and resource benefits.
Note that you may need to open up permissions for BizTalk to listen see here or here
Publishing and 'refreshing' the WSDL in a dev environment so that peer systems can create proxies etc can be a pain. After using the publishing wizard, you can use this tool to refresh your WSDL publication without having to redo the wizard.
http://www.microsoft.com/en-us/download/details.aspx?id=21973
Use the "BizTalk WCF Service Publishing Wizard". It will walk you through all the steps you need.
There is a web service application hosted On IIS 7.5. Authentication mode is Windows. When calling web services through my application, useDefaultCredentials atttribute on web service client is false. So web service call made on behaf of anonymous user. And also anonymous authentication mode enabled on IIS for the web service application.
To call web services successfully, I have to give read permission to everyone on folder which the web service application resides. But this causes to folder can be reached and read from everyone.
How can I hide the folder to be seen by everyone in this case?
If I am not successful to describe the issue, I can give you detailed explanations of specific points you want to understand.
I found the solution. I granted read permission for the built-in IUSR account and removed read permission for the everyone. So in this way, anyone on the domain cannot read the folder contents anymore.
After not getting much help on the last question, I decided to blow away the VM and re-create it as I already lost a week on this issue. And of course still issues, btu a little different.
I am using WSS on a 2008 server. I removed from the SharePoint admin the blocked asmx page types. I am using the administrator account with password and the domain, which is the IP of the VM machine. Normally I would never recommend using the admin account, but since I am just running a test to connect to SharePoint web services, so be it.
When accessing this site via a webbrowser, no issues whatsoever.
When accessing the web services from the browser using the admin credentials, no problem.
Then when trying to access the web service via Visual Studio I get the windows security dialog;
Followed by a discovery credential for the list;
Followed by another Discovery Credential for access to the error.aspx page, but as you can see, I can see the list of services for lists.asmx;
Followed by yet another Discovery Credential asking for permission to the $metadata and this just continues continually -it will NEVER authenticate via visual studio 2010;
And then, of course, when the code is ran, what do we get - ACCESS DENIED.
Call made; code not listed makes connection.
Make call to service:
And receive the error.
And IIS for SharePoint is set top Windows Authentication and Impersonate. All defaults.
It has now been going on 5 days; does anyone at all have any clue as to what is causing this? I have used this code and technique for years with Windows Server 2003 and WSS 2.0 and / or MOSS 2007 connecting from remote machines and NEVER, I mean NEVER had issues like this.
I would really appreciate any help.