Does anyone know how we can authenticate customer’...
# suitescript
b
Does anyone know how we can authenticate customer’s contacts other than using the soon to be deprecated user credentials? A couple of years ago I’ve created a RESTLet and used the user credentials mechanism to authenticate customer’s contacts via a 3rd party web portal. Since the user credential authentication for RESTlet will soon be deprecated I am trying to investigate how customer’s contacts can be authenticated. I am not able to create any tokens for this this type of entity since tokens can only be created for users. So the current flow is that a customer’s contact visits a 3rd party web portal and tries to login by using their NetSuite credentials. The 3rd party web portal then pass these credentials by sending a request to the RESTlet. The data passed includes the NLAuth authorization header. When the supplied credentials are valid then the RESTlet will simply return a success which makes sure the customer’s contact can login into the 3rd party web portal.
b
im not sure if that works for customer center based roles
s
Customer center can work with SSO. We are implementing a project based on that right now. There are some issues with it, for instance you cannot specify which role to use, so each customer center user must have only one customer center role, otherwise a role will be chosen randomly.
b
Thanks for the tips. I’m looking into Inbound SSO.
So inbound SSO is also deprecated. Well good job NetSuite :S
@battk no, we need the other way around users are logging in into the 3rd party web portal and will never need to log in into NetSuite
Unlike the below diagram, users and to be precise customer’s contacts’, need to login into a 3rd party portal. They aren’t using NetSuite directly.
I came up with a Node.js example yesterday in which a request will be made to the customer login form. I then check the HTTP response code and if it’s a 302 then the user could be logged in. In the event of a HTTP response code 200 the user could not be authenticated.
all other calls the 3rd party web portal makes will be handled via another integration where TBA is involved so that part is already done