This topic was automatically generated from Slack. You can find the original thread here.
external auth no longer visible when creating workflows - see second image for what i am getting, first for what it should look like.
Hi , we’re making modifications to external auth — in the meantime you can use Project Env Vars and/or pass your credentials to your workflow at runtime via HTTP. You can set the pd-nostore flag to 1 on requests with credentials to disable logging for those requests only. See more here
Then you’ll be able to reference the external auth tokens in a custom code step
in reality nothing in your visual builder will work with your approach right? I cannot see how that could be implemented - if you reference the screen above - you can pass credentials through in the trigger but then what? this has completely broken external auth as far as i can see.
I’ll check with the team and get back to you
Hey , sorry about that, had you been using it previously? If so, happy to re-enable it for you. Can you tell us more about your use case? And when you get a chance please let us know your workspace ID, which you can find in your workspace settings.
Danny,
please re-instate external auth ASAP.
My workspace name is: staffhub
ID is: o_8LIrm4w
I have built my entire project around the use of external auth - in fact i just finished a Nango project to make it work. I was talking to the Nango founder about giving better support for Pipedream users so that their free auth option was a bit more accessible.
Basically Pipedream runs all the webhook functions for my AI voice assistant - I am now in the process of going from validation to MVP launch and so need to be able to pull in customer auth.
I am doing my customer accounts in wordpress - so pretty limited as to what I can do on the backend. Nango validation is working from there and now I am rolling out external auth through all my workflows.
This is an essential feature that I have built my entire project around.
kind regards,
Jorian
Just confirming that I responded via email
Danny,
External Auth is still not working.
happy to work with you to test the connect feature - very disappointed that external auth is still not working for me though. That is literally my whole project put on hold.
I do user management on wordpress - I can’t see the connect feature working for me - I can only run javascript - which is sufficient for Nango but doesn’t look like it will work for your new connect feature.
My use case is fairly simple -i have users on wordpress who authorise their google accounts using Nango. Then I do external auth using the token from Nango.
If you could get my external auth operational that would be great.
Jorian
im going to try the connect link. here is my php code. will let you know if ic an get this to work: <?php
function pipedream_connect_button_shortcode() {
// Check if user is logged in
if (!is_user_logged_in()) {
return ‘
Please log in to connect your Google account.
’;}
// Get current user's email
$current_user = wp_get_current_user();
$user_email = $current_user->user_email;
// Initialize Pipedream client
$pd_client = new PipedreamClient([
'publicKey' => 'YOUR_PIPEDREAM_PUBLIC_KEY',
'secretKey' => 'YOUR_PIPEDREAM_SECRET_KEY'
]);
try {
// Create a connect token using user's email as external_id
$token_response = $pd_client->connectTokenCreate([
'external_id' => $user_email
]);
// Construct the connect link
$connect_link = sprintf(
'https://pipedream.com/_static/connect.html?token=%s&connectLink=true&app=google',
$token_response['token']
);
// Return the button HTML
return sprintf(
'<div class="pipedream-connect-button">
<a href="%s">
<img src="https://staffhub.ai/wp-content/uploads/2024/10/google-signin-button-small.png"
alt="Sign in with Google"
title="Click to sign in with Google">
</a>
</div>',
esc_url($connect_link)
);
} catch (Exception $e) {
return '<p>Error: Unable to generate connection link. Please try again later.</p>';
}
}
add_shortcode(‘pipedream_connect’, ‘pipedream_connect_button_shortcode’);
// Simple Pipedream client class
class PipedreamClient {
private $publicKey;
private $secretKey;
private $baseURL = ‘https://api.pipedream.com’;
public function __construct($config) {
$this->publicKey = $config['publicKey'];
$this->secretKey = $config['secretKey'];
}
private function getAuthorizationHeader() {
return 'Basic ' . base64_encode($this->publicKey . ':' . $this->secretKey);
}
public function connectTokenCreate($opts) {
$response = wp_remote_post(
$this->baseURL . '/v1/connect/tokens',
[
'headers' => [
'Authorization' => $this->getAuthorizationHeader(),
'Content-Type' => 'application/json'
],
'body' => json_encode($opts)
]
);
if (is_wp_error($response)) {
throw new Exception($response->get_error_message());
}
$body = json_decode(wp_remote_retrieve_body($response), true);
if (!isset($body['token'])) {
throw new Exception('Invalid response from Pipedream API');
}
return $body;
}
}
Let me know if that works for you, also please let me know exactly what isn’t working with External Auth so we can fix it.
external auth is now available thanks - please let me know if you recommend i migrate to connect links - if you are going to deprecate external auth I will work on the connect link.
Great. If that’s working for you for now, then that sounds good. We don’t have plans to deprecate that feature, but we also aren’t focused on making changes to it in the near future, we’re very focused on Connect right now.