Custom Tab / Components - Inherently awkward / insecure? - 03161332

Forum for users and developers of Bullhorn's new REST API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
markggn
User
Posts: 1
Joined: Sun May 06, 2018 12:08 pm

Custom Tab / Components - Inherently awkward / insecure? - 03161332

Post by markggn » Sun May 06, 2018 12:16 pm

Hey guys,

I'm trying to figure out how to integrate our application partially using the custom tab functionality. We're hoping to place forms and actions that ought only to be available to authenticated users of both our app and Bullhorn, but the parameters we receive on the iFrame don't provide any security boost particularly. For example, a custom tab for the Candidate entity will yield the following params on the GET request for our iFrame:-

EntityType: Candidate
UserID: x
CorporationID: y
PrivateLabelID: z
EntityID: n

I can't see any (seamless) way of using this that prevents someone from just loading the same URI Bullhorn generates (easily found in the source code) and requesting this directly. Is there further authentication / trust I can leverage here? The only option I can see here is asking the user to log in to Bullhorn (OAuth stylee) via the iFrame even though they're already logged in.

Any tips appreciated!

Post Reply