Need a help on how to add a realm for a example.
com.worklight.integration.auth.AdapterAuthenticator
How should i put this realm to server?
That's got nothing to do with your application server.
You define Realms in the MobileFirst project that you created using either MobileFirst Studio or the CLI tool (in which case you then edit a file in whichever code/text editor of your choosing).
In both cases the file to edit is called authenticationConfig.xml and is located in the your-project\server\conf\ folder.
Before touching this file, though, you should familiar yourself with the authentication concept in MobileFirst Platform because you do not simply "add a realm". You are required to also configure its associated Login Module and security tests as well as actually utilize it somewhere in your application's logic.
Please read:
Developer Center: Authentication and Security
Knowledge Center: MobileFirst Security Framework
The tutorials and documentations topic above will also lead you to Adapter-based authentication, which is what you are supposedly actually looking for.
Related
I am using an Azure WebApp with development slots running a netcore aspnet install. How often are these instances patched and how are they patched?
Is there any way for me to see a log of exactly when they are patched?
If you are referring to the app itself in Azure App Service when you deploy a Web App from the gallery you get an install of whatever item you selected. That item will not be automatically updated, if they try to update the container this will most likely break your application especially if you had customized that container in any way.
If you are referring to the OS, Microsoft will update the OS and IIS version from time to time and when they do, if there is any possibility of this affecting your app there will be an e-mail sent to the e-mail account registered under the subscription notifying him/her of the maintenance. Normally you shouldn't experience any downtime.
You may also check the Operating system functionality on Azure App Service and Kudu Console for more details.
Hope this helps.
I have an asp.net website that I'm looking to migrate over to Azure. I have been doing some analysis of the website and code to understand issues with the migration. I am confident that 95% of the code will be fine as most of it is pretty standard web forms and dot net programming.
However, I have just run across an ActiveX component that is installed into the \windows directory on the webserver.
I am wondering if this will be an issue for the migration? There could easily be a number of follow-on questions as well depending on the answer. How do Azure web roles handle instantiation of activeX server components? Can I include the DSINTX.OCX file into the solution or do I wrap it in a dotnet assembly?
private DSINTXLib.Dsintx m_dsintx;
...
m_dsintx = new DSINTXLib.DsintxClass();
Installation of the ActiveX component should not be difficult. You can use a startup task running elevated to install it, assuming that there's an unattended installation mode for it. I blogged about this process for a Windows Service a while back.
http://blogs.msdn.com/b/golive/archive/2011/02/11/installing-a-windows-service-in-a-worker-role.aspx
If you don't have an installation file, then create a script that installs and registers the control and then use RDP to your role instance to debug. The blog post goes over some of these techniques as well. (Use notepad to create the command file, not VS.) You can add the OCX to your project, but be sure to set the Copy Local property to True so it becomes part of the package that is sent to Azure.
Ok, horrible headline, but the question is, has anyone used the new WACA? I run the scan and for most IIS related Rules I only get "Indeterminate".
For example:
In element enabled attribute is set to false -> Indeterminate
And that should be something that the tool can determine? No?
Cheers
Remy
IIS Common Files are required to scan for most of the web server checks. IIS Common Files are native in 2003/XP, but not 2008/Vista/Win7 so you need to install the IIS 6 Mgmt Console, Metabase, and Configuration Utility. Unfortunately this needs to be installed on both the scanning host and the remote server. Why they don't leverage the built-in IIS7 features instead of making you expand your attack surface I don't know.
See this page for instructions for installing IIS Common Files: http://technet.microsoft.com/en-us/library/aa998413%28EXCHG.80%29.aspx.
when I clicked on Browse *;80(http) I got this screen in IIS..what could wrong? please give me solution.
Try installing the ASP.Net Frameworks.
Also check whether you have configured web config file in a proper manner.
All frameworks are very important as far as the configuration goes.
Hope this helps!!
The issue you are running into is a common problem for developers since they start developing on their Desktop or their Documents folder without realizing that only they have access to them. In other words those folders only have ACL's for you. This works ok when you use Visual Studio since they run the process as your identity which makes it all work, however when you use a real server, such as IIS that runs as a service it will no longer run the process as your identity but some service account which will NOT have access to your directory.
You will need to add ACLs for IIS to be able to read the files (IIS_IUSRS or the AppPool Identity like IIS APPPOOL\DefaultAppPool, depending on the settings of your apppool), or move it to a folder that has enough access such as \inetpub\wwwroot\
We are developing client application for our solution. Its a desktop client. We are using flex for same. (Although I know flex is meant for web application and air application is best suited for desktop clients, but due to some build issues we can't go for air applications). Now according to our use case we required to read file from local file system which is not allowed in flex application due to sandbox policy. To override it we had planned to use it in local mode (i.e. running from local file system instead of deploying in web container). So after running application in local mode it bypasses sandbox policy and allows to read local file. Eventually we requires remote services call (either using web services or blaze ds) also in our application. To avoid sandbox restriction for network access in local mode we are planning to explicitly grant network access permission to our flex application. So does anybody finds any issues in this approach which I may encounter ?
Thanks,
Ankur Shah
As long as you make sure to use the local-with-networking security sandbox. This will allow you to access both the local file system and the network.
You can see more about the different sandbox types here: http://livedocs.adobe.com/flex/3/html/help.html?content=05B_Security_04.html
We had to avoid any of these kinds of issues by using Air with C# WebServices and HttpServices (twas an Air GUI with C# server-side running on Windows). Although not much help to you.
Another possible solution might be to use JavaScript within Internet Explorer to access the local file system via ActiveX controls (which I hav'nt done), and then use Flex's ExternalInterface API to grab the JavaScript/Html data from within the same browser (which I have).