Connect Smooch with agent's platform - smooch

Just two questions, Smooch has a live agent's platform? or it should connect to other Zendesk products like Zendesk Support?
If Zendesk Support is needed, there is a way to connect it automatically or I need to connect it through webhooks?

You have a few options when using Sunshine Conversations:
Link your existing Zendesk Support subdomain to your Sunshine Conversations account (contact support#zendesk.com to start the migration process)
Use an official integration from the Marketplace to link it to another Business System: https://app.smooch.io/integrations/categories/business-systems
Build an integration to any other Business System using our APIs: https://docs.smooch.io/guide/api-quickstart/

Related

Using external IdP to authenticate to Banno

We want to utilize an external IdP that provides authentication services with Banno. Is there an option to configure it as OIDC IdP and redirect users to authenticate with it?
looking through Banno authentication framework I only see references to pulling data from Banno assuming user was already authenticated. Cannot find any documentation to how to configure redirect-to-IdP for authentation
We don't have documentation specifically about that use case, but we do have docs about our support for OpenID Connect Discovery: https://jackhenry.dev/open-api-docs/consumer-api/api-reference/v0/oauth-and-openid-connect/#openid-connect-discovery
We're aware of folks using Amazon Cognito, Kong, and Firebase with our OIDC Discovery endpoint.
Note that those services may not support Proof Key for Code Exchange (PKCE). If that's the case, then you'll have to have Banno Admin for your financial institution turn off the "Require PKCE" option in the External Application.

How do I create an Azure Dev Ops release to publish to another organisations tenant

I have created a web application as a private developer for a friends company. All the code lives within my personal Azure Dev Ops portal and at present has a pipeline configured to build and a release configured to release to a web application within my Azure tenant.
How can I now create a new release pipeline so that the code will be published to the a web application within the companies official Azure tenant?
We have created an Azure subscription and a web application using my friends company office 365 account but I somehow need to grant access or authorise my personal Azure Devops portal to publish.
After a lot of searching and playing it would seem there are many many ways to do this. In the end I went down the route of adding my friends work account to my Azure DevOps project so that they could create a service connection by authorising with their Office 365 account.
Once done I gained access to the subscription when creating the release.

FIWARE: The usage of Identity Management GE

I want to use Identity Management - KeyRock GE in the FI-LAB portal (https://github.com/ging/fi-ware-idm/wiki/Using-the-FI-LAB-instance). It's said that this GE is already deployed on FI-LAB.
Can I use this GE just to control an access to my application or is there any other usage of this GE?
Also, how will it work (step-by-step) when a registered user wants to login into my application?
You have two options here. You can use the current instance of the IdM in order to offer you the authentitation and authorization or you can install your own instance of Keyrock. I recommend the first one in which you just need to create an account in the FIWARE Lab and use the keyrock to offer you security access to your applications. I think that you can go to this presentation Adding Identity Management and Access Control to your applications. in order to have deep details about the different steps that you have to follow to do the first scenario.

FI-WARE Identity Management - Integration with 3rd party providers

I read about the FI-Ware Identity Management GE.
I understand it acts as an OAuth2 Identity Provider enabling users to log in into applications using their FI-Ware site credentials.
The FI-Ware catalog site states this about the IdM :
In addition to providing a native login, IdM supports the integration
of multiple 3rd party authentication providers. Foremost, it supports
in a first step the configuration of preferred identity providers
through the administrators. The use of 3rd party IdMs lowers the entry
barriers for a native user to register, since the user can link to
her/his preferred IdM and use this account for authentication.
However, I could not find an explanation how this can be done.
Can anyone help ?
Thanks!
IdM doesn't support authentication with other IdP's. What that paragraph explains is that developers can use third party authentication in THEIR services using other IdP such us Google, Facebook or Keyrock. So what IdM supports is to allow other services to login using IdM authentication.
BR

CAS server with SAML.2

I'm starting to work with CAS on my company. This is totally new for me, so I had to read lot of documents and how to's to have an idea of how CAS works.
So, we have to provide a single sign on service in our server to a company with two different applications. One of those, uses SAML2.
My CAS server is now working against a MySQL database, so I'll have the users of those 2 apps on my database to provide authentication service.
What I don't get clear is about SAML. All the tutorials I've read about SAML2 integrated with CAS 4.0.0 are using Google Accounts. I don't know why! I have some SAML2 configuration on a xml on my CAS directories, but I don't know how to prove if it's working or not.
If you are going to authenticate both of the applications using your single database, CAS is enough, SAML not required. With SAML you can connect to an external application(which supports SAML), both might be having their own internal authentication, but they will commnicate each other through SAML2 protocol/agreement
CAS is ideal ,if you want to setup a web single sign-on to different web applications (exclusively for a single institution), which all use the same authentication (DB, LDAP or whatever). With this the authentication will be centralized for all these different applications.
For users from another external institution to use your web application, SAML would be the choice, provided the External application also should support SAML.