Aloha Miyako, I don’t quite understand what "urn:ietf:wg:oauth:2.0:oob" means, but I suspect you are referring to the Desktop app process of OAuth mentioned here: https://developers.google.com/identity/protocols/OAuth2InstalledApp
It basically does the request and response in 1 connection using this format for the redirect_uri: com.example.app:/oauth2redirect I don’t see that possibility listed in Blackbaud’s documentation so I’ll ask. The documentation says the following, so I kind of doubt it: "Since this is a redirection-based flow, your application must be able to interact with a web browser and receive incoming requests (via redirection) from our OAuth endpoints." They do have 2 types of OAuth connections: Implicit Flow (which is what I based my first plan on): https://apidocs.sky.blackbaud.com/docs/authorization/implicit-flow/ Authorization Code Flow (allows for refreshing tokens): https://apidocs.sky.blackbaud.com/docs/authorization/auth-code-flow/ The second one is better as I don’t have to “allow” every time. -- Sannyasin Siddhanathaswami Saiva Siddhanta Church Kauai’s Hindu Monastery 107 Kaholalele Rd Kapaa, HI 96746 808-822-7032 x102 On August 24, 2016 at 10:16:39 PM, Keisuke Miyako (keisuke.miy...@4d.com<mailto:keisuke.miy...@4d.com>) wrote: it depends on whether the service provider supports "urn:ietf:wg:oauth:2.0:oob" ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
