Salesforce SOAP API login Retirement
Dec 2, 2025
Show More Show Less
View Video Transcript
0:08
Hello everyone. In this video, we are
0:10
going to see Salesforce SOAP API login
0:15
method retirement.
0:17
Starting summer 27 release in
0:19
Salesforce, the the SOAP API login is
0:24
going to be retired.
0:27
The alternative approach for this is to
0:29
make use of
0:32
oath 2.0 flows instead of making use of
0:37
soap API login method.
0:42
If you have a requirement where you
0:45
wanted to
0:47
check how this particular uh retirement
0:51
is going to be affected in your org
0:54
before the retirement then you can make
0:56
use of the release update. If you go to
1:00
release updates in Salesforce setup find
1:03
the SOAP API login method retirement.
1:09
Go over all this information.
1:12
Also check all the steps that are
1:15
available in this SOAP API login method
1:17
retirement knowledge article. Once you
1:20
have completed once you have a good
1:22
understanding on this particular SOAP
1:24
API login method retirement, click the
1:28
done button. Once it is done, you will
1:31
be able to en enable test run and also
1:34
you will see a button called disable
1:36
test run. when you click enable test
1:39
run.
1:40
So before enabling this test run I'm
1:44
able to make
1:48
SOAP login request
1:50
with the username and password and I'm
1:53
able to get the session ID.
1:58
So now
2:01
if this particular SOAP ABA login method
2:04
is going to be retired then I wanted to
2:07
simulate it in my org. In order to
2:10
simulate it I'm going to enable test
2:13
run.
2:15
So the SOAP API login method retirement
2:17
is enabled in my Salesforce or
2:21
now if I so now previously before I
2:25
clicked that enable test run method I
2:28
was able to get the session ID by making
2:32
a post request to my SOAP API endpoint.
2:36
Now since I enabled it instead of
2:41
getting 200 I should get Salesforce
2:43
internal error message. Now let's click.
2:46
So before that let me clear the
2:48
response. I click the send button. Now
2:51
I'm not able to get the session ID. I'm
2:53
getting 500 server error. I'm getting
2:56
this 500 server error because
3:00
the SOAP API login return is enabled in
3:03
my org. I was able to simulate
3:06
when Salesforce actually retires this
3:10
SOP API login retirement. You can keep
3:13
it enabled if you get any um
3:19
uh request from other departments in
3:22
your uh in your uh company that they're
3:25
unable to connect with Salesforce then
3:28
you will know how to then you should
3:30
know how to roll back. If all other
3:33
integrations are already using
3:35
Salesforce
3:36
standard best practices of rest API with
3:39
O 2.0 zero flows then you can keep it
3:43
enabled. But if you get any compliance
3:46
then what you can do is you can click
3:47
this disable run test run so that you
3:50
will be able to roll back the changes
3:53
and the other applications which are
3:54
trying to connect to Salesforce using
3:56
SOAP API login method will be able to
3:59
connect and then they will be able to
4:00
generate the session ids to proceed
4:03
further. So the main uh uh way to roll
4:07
back the change is to click the disabled
4:10
test run.
4:12
So I'm going to keep it like this uh so
4:15
that no S soap API login method requests
4:19
are coming to my Salesforce or
4:26
in Salesforce setup under user interface
4:29
we have enable SOAP API login method
4:33
uh checkbox. This will be
4:38
available when we get a new org. In the
4:42
new org when you click enable soap API
4:44
login method and then if you click the
4:46
save button here we won't be able to
4:49
revert the changes.
4:52
So it's how it is designed by default
4:55
whenever this enable soap API login
4:58
method is enabled under user interface
5:00
we cannot roll back that changes.
5:04
So this will stay
5:07
enabled.
5:09
So even here I clicked enable test run
5:14
still this enable so P A P A P A P A P A
5:15
P A P A P A P A P API login is checked.
5:18
So this is not something which we can uh
5:22
control it. So once it is enabled, it is
5:24
permanently enabled in your Salesforce
5:26
or so. So no point in finding a backend
5:30
process to disable it.
5:36
Please check the video description. In
5:38
the video description, I have shared my
5:40
blog post.
5:42
From the blog post, you should be able
5:44
to get the additional information and
5:46
also the information what we talked
5:48
about it in the video.
5:51
I have also shared the Salesforce
5:53
referenced article for your reference.
6:01
I hope it was helpful.
6:08
Thank you for watching.
#Business & Industrial
#Computers & Electronics
#Internet Software
#Internet & Telecom
