LoadRunner SAML Login Script Help
Budget: ₹600 – ₹1,500 INR
I am recording a VuGen script for an InforLN ERP web session that authenticates through ADFS with SAML. My main hurdle is correlation and parameterization—especially capturing the dynamic SAML assertions and any anti-forgery or relay tokens that appear during the redirects. I also need clear, step-by-step guidance on the ADFS side so I know exactly which endpoints and certificates the script must reference and why.
What I am after
• A working LoadRunner 2023 (or later) script that logs in, reaches the ERP landing page, and can run in a multi-user scenario without replay errors.
• Inline comments that show where each dynamic value is captured and how it is reused.
• A brief walkthrough call or screen-share explaining the correlation logic, VuGen functions you used, and any parameter files you added.
• A concise checklist of the ADFS settings you verified or changed so I can repeat the setup in other environments.
Acceptance criteria
• Script completes the full SAML handshake and lands on a post-login URL with HTTP 200 for at least five sequential iterations in Replay.
• All tokens/IDs are captured at runtime—no hard-coded values.
• No “Login failed” or “Invalid SAML” messages in the server response.
• Works when user credentials are supplied from an external .dat parameter file.
Tools & notes
LoadRunner VuGen, Web/HTTP protocol, possible use of web_reg_save_param, web_reg_save_param_ex, and web_add_auto_header.
If you have proven experience handling SAML and ADFS in LoadRunner and can teach as you deliver, let’s get started.
What I am after
• A working LoadRunner 2023 (or later) script that logs in, reaches the ERP landing page, and can run in a multi-user scenario without replay errors.
• Inline comments that show where each dynamic value is captured and how it is reused.
• A brief walkthrough call or screen-share explaining the correlation logic, VuGen functions you used, and any parameter files you added.
• A concise checklist of the ADFS settings you verified or changed so I can repeat the setup in other environments.
Acceptance criteria
• Script completes the full SAML handshake and lands on a post-login URL with HTTP 200 for at least five sequential iterations in Replay.
• All tokens/IDs are captured at runtime—no hard-coded values.
• No “Login failed” or “Invalid SAML” messages in the server response.
• Works when user credentials are supplied from an external .dat parameter file.
Tools & notes
LoadRunner VuGen, Web/HTTP protocol, possible use of web_reg_save_param, web_reg_save_param_ex, and web_add_auto_header.
If you have proven experience handling SAML and ADFS in LoadRunner and can teach as you deliver, let’s get started.