Posts

Showing posts with the label authentication

request using HTTP Outh 2 authentication with PHP curl not work?

request using HTTP Outh 2 authentication with PHP curl not work? I have set up a http request using PHP CURL with following code. PHP CURL <?php $para='{ "payment_method": "bacs", "payment_method_title": "Direct Bank Transfer", "set_paid": true, "billing": { "first_name": "John", "last_name": "Doe", "address_1": "969 Market", "address_2": "", "city": "San Francisco", "state": "CA", "postcode": "94103", "country": "US", "email": "john.doe@example.com", "phone": "(555) 555-5555" }, "shipping": { "first_name": "John", "last_name": "Doe", "address_1": "969 Market", "address_2...
Post a Comment
Read more

Which oauth or openid-connect I need to choose in order to build a public sdk?

Which oauth or openid-connect I need to choose in order to build a public sdk? I am going to build an SDK for developers to access my backend restful resources. For example, I defined below restful apis: get GET /changes/changeId list GET /changes getStartPageToken GET /changes/startPageToken I need to secure my apis and I come across openid-connect, auth1 and auth2 but I am not sure which one I need to use. As far as I know, auth2 is more used to third-party authentication like login as google , facebook account etc. Is this right? google facebook In some other public APIs design, a developer need to register a developer account and get an app key and secret. They can use the key and secret to use their APIs. Which type of this authentication is it? Which one among them is more appropriate for my use case? Did you find an answer for this ? – Kavindu Dodanduwa 1 hour ago ...
Post a Comment
Read more

The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Negotiate,NTLM'

The HTTP request is unauthorized with client authentication scheme 'Basic'. The authentication header received from the server was 'Negotiate,NTLM' I am trying to connect to a service using the following settings. <bindings> <basicHttpBinding> <binding name="EngineSoap" closeTimeout="00:01:00" openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00" allowCookies="false" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" maxBufferSize="2147483647" maxBufferPoolSize="524288" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered" useDefaultWebProxy="true"> <readerQuotas maxDepth="32" maxStringContentLength="2147483647" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTabl...
Post a Comment
Read more

Laravel Passport - which grant to use for my users apps?

Laravel Passport - which grant to use for my users apps? I have application where users can register and add their own applications (websites, mobile applications). For each of these applications, I want to give access to my API and allow to get products form my database. For example: User X signup in my app, adds his blog user-X-blog.com and get access token. Next he can call to my API and get some products to show on his blog post. Which grant should I implement to make my API based on Laravel Passport safe and useful (each user application with its own token, no user login required to make api call, long-lived tokens)? Is it good idea to create for each user apps dedicated client and use client credentials grant? It doesn't look very safe for me (or maybe I'm wrong). 2 Answers 2 In your situation I think using Personal Access Tokens is the best option: Each unique user who signs up and ad...
Post a Comment
Read more