I downloaded and unziped ODL 11. I entered to the karaf interface and installed some features like:
feature:install odl-restconf (and some others)
After that action I can see (with netstat) the port ipv6:8181 openned.(Before that action the port was not openned) So It's important to install some features to open this web access port.
I access to http://myip:8181/index.html from my browser
But It returned:
HTTP ERROR 401
Problem accessing /index.html. Reason:
Unauthorized
What should I do?
There isn’t anything available on /index.html. RESTCONF is mounted under /restconf and provides access to the config and operational datastores, and you can see that if you have an identifier (see the ODL wiki for details).
If you want to see something without knowing an identifier, install the odl-mdsal-apidocs feature and open http://localhost:8181/apidoc/explorer/ (replacing localhost as appropriate).
Related
I downloaded latest version of ODL 15. I entered to the karaf interface.
as given in https://docs.opendaylight.org/en/stable-phosphorus/developer-guides/developing-apps-on-the-opendaylight-controller.html
I access to http://myip:8181/index.html from my browser
But It returned:
HTTP ERROR 401
Problem accessing /index.html. Reason:
Unauthorized
i tried to install features like odl-mdsal-apidocs, but not able to. giving error "Error executing command: No matching features for odl-mdsal-apidocs"
What should I do?
new releases from odl doesn't support dlux which is the gui of OpenDayLight
you can fix it by using older release like carbon
I am updating from Windows 7 to a Windows 10 on a 64 bit system. I have no problems updating and checking out projects from the Subversion server on the Windows 7 box. I downloaded the latest 64 bit version and installed it on the Windows 10 box with no issues.
On the Windows 10 box I can post an update, but I cannot check out a project from the repository. When I attempt to logon the server I get the following error message:
svn: E170013: Unable to connect to a repository at URL 'https://svn.example.com/!/%23MyRepo/'
svn: E175003: The server at 'https://svn.example.com/!/%23MyRepo/' does not support the HTTP/DAV protocol
message that says The server does not support the HTTP/DAV protocol.
I passed the error message to the server manager and was told the problem was with the TortoiseSVN app settings. I cannot find a setting in the app that would address the problem.
Anyone have any suggestions on how I can fix this issue?
You get this error message because the URL is invalid. It leads to a web interface (i.e. a web client) and Subversion clients do not know how to parse this URL. Please, see the following article - KB102: Subversion client errors caused by inappropriate repository URL.
The comment by Bahrep is the correct answer, but since in the comments there seems to be some confusion, I decided to elaborate further.
"The error indicates that the URL used to address the repository using Subversion client is inappropriate. Most likely, the URL was copied from the web browser's address bar when exploring the repository through the web interface of VisualSVN Server. Subversion client programs are not capable of handling the syntax of such URLs. The appropriate URLs should be obtained by clicking the Checkout button in the web interface."
I got this error because I used browser link in the toroise interface, but I should instead click "copy repository url" in the svn and use that link. As simple as that!
I'm in the process of configuring the WSO2 IS 5.0.0 Dashboard. I've followed this previous post to configure the gadgets: Cannot see any option in WSO2 Identity Server dashboard
since they weren't showing up/displaying properly.
In the config files though everything is HTTP. I plan on using a proxy and having everything behind HTTPS. Therefore, I'd like everything in the config files to be HTTPS.
I tried changing everything in the the config files mentioned in the above link to HTTPS and included port 9443, but when I go to the dashboard the gadgets are missing. I also tried leaving off the 9443 and just having https://ip-address/.... but it the gadgets and everything will not show up.
Are there additional files, other than the ones mentioned in the link, that need to be configured? Is it possible to have it set as https or can it only be http?
The issue you have mentioned in the previous post has been fixed in IS 5.1.0 and there are lot of improvements shipped with this version. Now you will be able to access all your gadgets via HTTPS without configuring in all the mentioned files. By default the dashboard and all the gadgets will be accessible through HTTPS protocol. But you can configure it by changing only in a single file now [1].
You can download the IS 5.1.0 from [2]
[1] {IS_HOME}/repository/conf/identity/sso-idp-config.xml
[2] http://wso2.com/products/identity-server/
I'm using the AJAX Test Server in Rational Application Developer. I'm posting a form to another host for authentication. That host takes a URL to redirect to after authentication. However, it insists on using HTTPS whenever it sends the 302 response. The low hanging fruit would be to just use HTTPS locally.
Looking at the launch configuration, the AJAX Test Server appears to be a custom Apache HttpCore server. I haven't spotted anything in the configuration guide.
Is there a way to access this test server via HTTPS?
This is for demo and local development purposes; not production.
Speaking from working with WAS (WebSphere Application Server) in RAD, I'm pretty sure the answer would be yes. The server (at least with WAS) has both secure and "unsecure" ports.
What I have noticed is that when the server is built with the install (at least with the newer versions of the products 7.5+), the ports used are different per install. This is to help with not conflicting with other applications that may use those ports.
So https is probably fine. You just may have to use it over port 302 or some other port.
If there is no admin console for viewing your ports, you could always try the Window | Preferences option under your menu items. Sometimes IBM hides server config stuff in there.
I'm testing a ClickOnce application deployment. I have setup a virtual directory on my machine (running IIS). I have specified http://localhost/SampleApplication as the Installation Folder URL in the Publish tab of Visual Studio. However, when I publish the application I get the following error:
Warning: Files could not be downloaded
from http://chrish/SampleApplication/.
The remote server returned an error:
(407) Proxy Authentication Required.
Publish success.
Warning: Unable to
view published application at
http://chrish/SampleApplication/publish.htm.
http://chrish/SampleApplication/publish.htm
Notice how it has changed my url from Localhost to my login name. Why? This wasn't happening a week ago.
ClickOnce installation involves verifying that the server name matches the expected name. Thus localhost always gets translated under the covers to the computer name [not the username as you suggest in your question] (one of many confusing things ClickOnce does - one side effect of this is that if you want to set up 3 download servers, you need to do 3 separate publishes and/or script the publish like this) or like this. So this is not a surprise - it's always doing that under the covers.
The 407 error relates to proxy auth. This implies downloading is being diverted via a proxy such as Microsoft ISA Server. Have a look in your IE Internet Options Connections Proxy Settings and make sure its bypassing for local addresses [such as chrish].
The reason it's reporting success is that the upload likely uses an alternate mechanism than the verification does and isn't being routed via / blocked by the proxy. (The underlying problem is that the .NET framework does not by default pass proxy credentials and you'd need to either apply a config entry for devenv or whatever does the publish or have the build process call a test step with extra code that does send the proxy credentials](http://blogs.msdn.com/jpsanders/archive/2009/03/24/httpwebrequest-webexcepton-the-remote-server-returned-an-error-407-proxy-authentication-required.aspx). See also How should I set the default proxy to use default credentials?)
ClickOnce doesn't like "localhost", but you can work around that.
If you set the Publishing Folder Location to:
C:\inetpub\wwwroot\SampleApplication\
and the Installation Folder URL to:
http://chrish/SampleApplication/
(where "chrish" is the network name of your computer) then you can publish locally.