How to resolve 404 error in Shibboleth Service Provider? - saml-2.0

I have installed the Shibboleth SP[2.5.6 latest] in my Windows Server R 2012.I followed the links :
Shibboleth Installation
I verified the installation and ran this sitelink -https://localhost/Shibboleth.sso/Status
It throws ERROR.
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

This error is due to, the default site with id '1' may be in stopped state. Restart the default site and check.

Related

Using MSAL in CloudShell

I've validated the MSAL auth path using the desktop PowerShell 5.1 and 7.0 applications. However, all of the authentication paths which worked on the desktop are not working in CloudShell -
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams
Connect-MicrosoftTeams: One or more errors occurred. (Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com )
Connect-MicrosoftTeams: Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com
Connect-MicrosoftTeams: No such file or directory
Connect-MicrosoftTeams: One or more errors occurred. (Unable to open a web page using xdg-open. See inner exception for details. Possible causes for this error are: xdg-open is not installed or it cannot find a way to open an url - make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com )
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams -UseDeviceAuthentication
To sign in, use a web browser to open the page https://microsoft.com/devicelogin and enter the code BRZPG2UNE to authenticate.
Connect-MicrosoftTeams: One or more errors occurred. (Windows Data Protection API (DPAPI) is not supported on this platform.)
Connect-MicrosoftTeams: Windows Data Protection API (DPAPI) is not supported on this platform.
Connect-MicrosoftTeams: One or more errors occurred. (Windows Data Protection API (DPAPI) is not supported on this platform.)
PS /home/michael/CSTest/0.0.2/MicrosoftTeams> connect-microsoftteams -AccountId miluong#microsoft.com
Connect-MicrosoftTeams: One or more errors occurred. (Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error: )
Connect-MicrosoftTeams: Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error:
Connect-MicrosoftTeams: Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error:
Connect-MicrosoftTeams: One or more errors occurred. (Federated service at https://msft.sts.microsoft.com/adfs/services/trust/13/windowstransport returned error: )
How do I enable support for managed identity?
How do I get interactive auth flow to work without xdg-open? Currently CloudShell does not install xdg-open
Is there a recommended path to try to acquire a token without DPAPI? CloudShell works in a Linux environment and DPAPI only supports Windows.
Do you know of any PS modules which use MSAL that are working in CloudShell?
xdg-open does not work and is not planned to be supported in CloudShell
The DPAPI error was because I was trying to protect the token by encrypting it at rest
Integrated Windows Authentication is not a supported workflow in CloudShell because it's a Linux based environment.

Why do I receive a Service Unavailable message after running the project GWT?

I am creating a GWT project from the GWT Material official website using maven. I am following the tutorial offered by the site: http://gwtmaterialdesign.github.io/gwt-material-demo/#gettingstarted . Im getting this in the view page:
HTTP ERROR: 503
Problem accessing /index.html. Reason:
Service Unavailable
Powered by Jetty://
I tried all the solution proposed here but I failed to view the project homepage.
There is no error in the eclipse console. but when inspecting the home page im getting this error:
Voice Instead ready.
content.js:29 Object
favicon.ico Failed to load resource: the server responded with a status of 503 (Service Unavailable)
enter code here
after running the project
in the window Developement Mode in the Jetty console next to Developement Mode
i have problem with Jetty. i don't know
What is jetty and what it allows to do? Im getting this error :
`00:00:16,662 [WARN] Failed startup of context c.g.g.d.s.j.WebAppContextWithReload#3772b95a{/,file:/C:/Users/Mm/eclipse-workspace/com-gwtmaterial-tutorial/target/com-gwtmaterial-tutorial-1.0-SNAPSHOT/,STARTING}{C:\Users\Mm\eclipse-workspace\com-gwtmaterial-tutorial\target\com-gwtmaterial-tutorial-1.0-SNAPSHOT}
<pre>java.util.zip.ZipException: invalid entry size (expected 4178 but got 10926 bytes)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:384)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:196)
at java.util.jar.JarInputStream.read(JarInputStream.java:207)
at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:140)
at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:118)
at java.util.jar.JarInputStream.getNextEntry(JarInputStream.java:142)
at java.util.jar.JarInputStream.getNextJarEntry(JarInputStream.java:179)
at org.eclipse.jetty.annotations.AnnotationParser.parseJar(AnnotationParser.java:915)
at org.eclipse.jetty.annotations.AnnotationParser.parse(AnnotationParser.java:831)
at org.eclipse.jetty.annotations.AnnotationConfiguration$ParserTask.call(AnnotationConfiguration.java:163)
at org.eclipse.jetty.annotations.AnnotationConfiguration$1.run(AnnotationConfiguration.java:548)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)</pre>`
I solved it by following the next step:
1- Close Eclipse.
2- Go to user directory and delete the .m2 directory.
3- Open Elipse.
4- Right click on the project -> Run as -> maven install

Remote implementation for app_identity_service.GetAccessToken failed at GAE PHP dev

Google App Engine SDK for PHP (at local environment) returns error on any try to use Google Cloud Storage. Error message is:
Fatal error: Uncaught exception 'google\appengine\runtime\RPCFailedError' with message 'Remote implementation for app_identity_service.GetAccessToken failed' in /media/data/home/vladimir/setup/gae/google_appengine/php/sdk/google/appengine/runtime/RemoteApiProxy.php on line 92
It exactly repeats the problem described here:
App engine update breaks CloudStorage in dev php env
Test code from the question above shows the same result.
I tried App Engine SDK for PHP versions 1.9.19, 1.9.20, 1.9.21 without success.
On Win10 this issue can be solved by generating an application-default credentials file:
D:\Workspace\Sourcecode>gcloud auth application-default login
Credentials saved to file: [C:\Users\Otje\AppData\Roaming\gcloud\application_default_credentials.json]
And then setting the environment in commandline:
D:\Workspace\Sourcecode>SET GOOGLE_APPLICATION_DEFAULT=C:\Users\Otje\AppData\Roaming\gcloud\application_default_credentials.json
Seems to me GAE on local just outputs limited error information when it can't find the right credentials to succesfully connect to remote endpoint.
It seems that it was GAE's server side issue. They fixed it. I discovered that it started to work as expected today without any changes applied by me.

WLP :: Worklight :: Can't install runtime

I'm using Worklight 6.2 server edition and I can't deploy a working runtime (of other environments) on my server.
I'm using webpshere liberty profile v8.5.5 and when I deploy the runtime via GUI it says success and on server.xml I can see the new configuration for the app.
However when I go to the worklightconsole I don't see my runtime to upload the app.
On messages.log there is a error regarding JMX connection.
The quoted error is
Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured
I'm refering this because I've seen some post on SO saying that these issues might be connected. However I have the restConnector-1.0 on my WLP features.
Reference: No runtime on my Worklight 6.2 Console after installing analytics
On messages.log there is some other things that I found interesting, like the correct start of the runtime I've deployed
[11/12/14 5:50:45:177 CST] 00000012 com.worklight.server.bundle.project.JeeProjectActivator I FWLST0002I: ========= Project /HelloWorld started. The project WAR file version is 6.2.0.00.20140922-2259,running on server version 6.2.0.00.20140613-0730. [project HelloWorld]
and two erros while starting my server
[11/12/14 5:50:49:911 CST] 00000012 SystemErr R 24 WorklightPU WARN [Scheduled Executor-thread-1] openjpa.Runtime - An error occurred while registering a ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root URL [file:/opt/IBM/WebSphere/Liberty/usr/shared/resources/worklight/lib/worklight-jee-library.jar]. The error has been consumed. To see it, set your openjpa.Runtime log level to TRACE. Load-time class transformation will not be available.
Second error:
java.lang.RuntimeException: Timeout while waiting for the management service to start up
I don't know what these are but I think it might be related to my problem and this errors eventually appear when I start my server.
Does anyone have any tips for troubleshooting this issue?
Thanks in advance.
This is a known issue from Websphere.
There is a APAR to fix that, a workaround is to restart the server with the --clean option to force a refresh onto the shared libraries.
http://www-01.ibm.com/support/docview.wss?uid=swg1PI17830

Tomcat7 breaking request parameter behaviour from Tomcat5.5 and Struts1.1?

I have a link which points to my servlet (Struts 1.1 App).
http://myserver.com/app/preview.do;jsessionid=1234567;p1=test;filename=/page2.htm
All was working fine in Tomcat5.5 and jdk1.6, but now with tomcat7 and jdk7, it does not work anymore. Tomcat now sends 404 error, because
/app/preview.do;jsessionid=1234567;p1=test;filename=/page2.htm" could not be found on server
So it tries to find the file page2.htm in path.
Does anybody know how to configure Tomcat to get it work again?

Resources