My ShinyProxy is up and running. If I use the authentication basic, it is working. I wanted to connect the ShinyProxy with my IdentityServer4.
Follow the documentation of ShinyProxy, I configure my ShintProxy as follow:
proxy:
title: Open Analytics Shiny Proxy
port: 8080
authentication: openid
admin-groups: scientists
openid:
auth-url: https://myidentityserver4/connect/authorize
token-url: https://myidentityserver4/connect/token
jwks-url: https://myidentityserver4/.well-known/openid-configuration/jwks
client-id: ShinyProxy
client-secret: password
When the user opens the browser to the ShinyApp, it is redirected to login page to the IdentityServer4. The user can login and then it is redirected to
http://myshinyproxyurl)/login/oauth2/code/shinyproxy
Unfortunately, the result is
or if I try on my laptop the error is slightly different
It seems there are too many redirections in the ShinyProxy.
Any ideas?
After a lot of research and study, I found how to implement Identity Server with ShinyProxy. I have created a complete step-by-step guide in my blog.
I hope it could help other guys.
Related
I have deployed wso2am-4.0.0, and configured sso with keycloak oidc. Everythin worked fine but logout failed, it didn't loutout from https://am-domain:9443/publisher.I am searching for a long time on net. But no use. Please help or try to give some ideas how to achieve this
I know nginx provide a way to login using basic authentication (with a password file). I wanted to know if there is a way to delegate the authentication to a dedicated server.
Here is the process I want to pursue :
- The user try to access to the nginx server without auth.
- Nginx ask for username and password.
- Nginx request the dedicated server with the provided credentials.
- If ok, nginx create a new basic auth for the user, and let the user pass in.
Thank you
I have configured 2 wso2 IS server instances in the local windows environment according to the documentation provided https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server+5.1.0%2C+5.2.0+and+5.3.0
and also the NGINX configuration with self signed certificates
I have been redirecting to the wso2 is login page of any one node but when logging in its redirecting to the login page again but at log showing
[2017-05-24 15:52:26,528] INFO {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - 'admin#carbon.super [-1234]' logged in at [2017-05-24 15:52:26,528+0530]
Its working properly with one node(other is down).
I am not able to figure out where is the issue, both nodes are working properly no error in the logs,
Please help ,
Thanks
Pankaj
You will need to enable sticky sessions in nginx configurations. See WSO2 doc too.
I've just installed Redmine on Windows 2008 R2 through the setup realized by Bitnami.
All works fine. Also SSL is working excellent.
Since today Redmine is in my DMZ, and I reach it directly, from internal network.
I arrive on login page and go.
Now I've published it on public IP with Microsoft TMG.
On TMG I use a listener that require authentication through radius.
TMG permits to pass credential to the web application by some different way, one is basic auth, one is NTLM....
I've found a redmine plugin that permit to use basic auth in redmine, so at login I don't see the redmine page but the classic http popup for credentials.
In this situation, like other published web application, TMG is configured to pass credentials on http basic auth but only redmine fails.
TMG pass credentials and these are refused by redmine, so TMG propose again credentials request.
Does anyone has a solution?
It could be a problem in the basic auth plugin, but it's the only one I've founded.
Thanks,
Mirko
QUESTION: Authenticating Drupal Users Using Remote Call to Active Directory Single-Sign-On(SSO), How do I do it?
SPECS(DRUPAL_SYSTEM): Linux-CentOS-5.X, Apache-2.X, PHP-5.X, Drupal-6.X
CONTROL(DRUPAL_SYSTEM): 100% control of Drupal server making call to Authenticating server using Active Directory Single-Sign-On
SPECS(SSO_SYSTEM): Currently Unknown, but run by same company
CONTROL(SSO_SYSTEM): None Currently, but run by same company
LEVEL_OF_KNOWLEDGE: Basic for all systems listed, but able to trouble shoot tech subjects.
Thanks in Advance!!
TAGS: drupal single-sign-on active-directory authentication
Modules:
Webserver
Auth Webserver LDAP
LDAP Provisioning
LDAP Integration