I have a situation where I currently call web focus reports from our JAVA web applications. But is not a secured way calling and I wanted to implement SAML authentication and pass parameters through SAML. Any help in this regard will be great help
Is there a reason you need SAML?
OpenID Connect is a much easier option.
For SAML, you need to implement a SAML stack.
There is more information here.
Related
I'm stack in my very first task of my very first job as Front-End developer, I know I am hindered, but I hope you will be able to help me.
My task is the same as in the title, to configure the frontend to use b2c for authentication, I don't have to impletement the authentication itself, just to configure the b2c, I will explain a little bit the project so that you can understand better:
They have a main App which is already working perfectly and it is stable, what they want to do is to build a platform aside, where the the customers can send their complains, on this platform every customer should login automatically with the credentials of the main App.
They provided me the entrypontins (for authorization, the token endpoint and the end session endpoint), the jwks uri and the cliendID, the App is build in Nuxtjs and they are using Azure AD B2C as directory service. The App is absolutely empty, it was just created and the configuration I have to do is the very first thing that should be implemented.
I have found a lot of theory informations on the web, but I cannot manage to find a guide that could help me to implement it practically, and the most of the practic tutorials/docs are about implementing the full process of authentication.
I am wondering if some of you knows a nice tutorial or guide or something that could help me to take a few steps forward.
I thank you all in advance !!
Does Mashery play nicely with a third party OAuth2/OpenID Connect provider? Can it be configured to allow OAuth2 tokens to pass through? If so, how much functionality of Mashery is lost by going with a different identity provider?
I am currently using IdentityServer4 but will soon be using Mashery and I'd like to understand the implications of using both.
Are you asking if Mashery support oAuth tokens generated by external parties ?
Answer is no. And I don't think they have any plans to implement it soon.
Could you please share how to Manage SAML post request from asp.Net Client application to ADFS server? Is there need any other configuration in client side?
In our case the ADFS server already configured, we need to implement that SSO in our asp.net application using SAML request. Could you please share your knowledge?
There is no built in support in the .NET framework for the SAML2 protocol. And don't write your own (I've done that, it's a LOT of work to do it right and secure). Find an open source or commercial SP (Service Provider) implementation for .NET and use that. There are plenty of them (disclaimer: I'm the author of one of the SP implementations, but to avoid a race from everyone with an SP implementation to post and recommend their one, I won't recommend any here).
I am building an AngularJS application with a Laravel API. I am looking for authentication for a couple of days, but I am stuck.
I found OAuth 2.0 as a kind of default authentication, also used by Facebook and Twitter and so more. A lot of tutorials I found are about using OAuth 2.0 with Facebook and Twitter or Google. But, I do not want to authenticatie a user with Facebook, but I want to build my own authentication, using the user credentials in my own database. So I guess, I need my own OAuth provider.
The authentication has to be very secure and easy to connect for other companies, who want to use our data (it is a web application for primary schools).
I believe there are a lot of answers possible on this question. But, I also believe a lot of people have the same question ;)
Who can explain me how to use OAuth 2.0 or a similar authentication method?
You are right - if you want to implement OAuth 2.0 you need to be your own provider (or authorization server). Being your own provider also means you can actually skip some parts of the process (e.g. the screen with a confirmation if the user really wants to grant this application the right to that etc...)
If you decide to go with OAuth 2.0, there's a widely used package called oauth2-server-laravel that helps with the whole process.
However you could also develop you're own token-based authentication system. Actually the basics are pretty simple:
Login
Verify credentials
Generate token
Store token in database
And then on request you check if the token is in the database (and hasn't expired yet)
Dead simple right? Well.. as you may already know, that's too easy to be true.
Especially where security is of high importance, You have to consider every case and you should really know what you're doing. That's why I recommend you use the OAuth standard. Yes, it may be a bit of an overkill but I believe it's worth it.
Hope I could help :)
I'm really new with SAML SSO. I'm woking with an idp webapp that will support SAML authentication.
The problem is that I will need that other sp authenticate with my idp and I don't want to implement all the protocol in every platform (Python, PHP, Java, etc).
I was thinking if there's a way to implement the sp authentication flow using an apache filter.
Has someone thought about this?
Thanks.
mod_mellon is what you're looking for: https://github.com/UNINETT/mod_auth_mellon
Using Shibboleth as a SAML client in conjunction with Apache web server may be an alternative.