Global Security Forum

Hi All,

I want to set sms notification ISVG, so if there's an AD account created it will sent sms notification that contain username and password in sms content to the user. I have sms gateway url, but I confuse on how to set it up on ISVG.

Here's for sms gateway url https://smsgw.test.co.id:5001/cgi-bin/sendsms?user=[user]&pass=[pass]&from=[sender]&to=msisdn&text=[sms_content]
And here are for sms notification configuration parameter on ISVG.

Questions:
1. Should I set the username, password, and port again in the sms url parameter? If yes, what attributes that should I put in url so we get the value from what I set in ISVG?
2. How's the attribute format from ISVG that I can use for "to" parameter in url as it should be the phone number of ther user?
3. and how's the attribute format from ISVG notification template that I can use for "text" parameter in url as it should be the sms body for the user?

Hopefully there are someone can help me for this or experienced for this.

Thanks.
Julian Fazri

Here are answers to your questions:

• Username, Password, and Port: In the SMS gateway URL, you already have placeholders for [user], [pass], [sender], and others. In ISVG, you need to map these placeholders to actual values. For instance, if ISVG has settings for username, password, and port, you'll use those settings to replace [user], [pass], and port in the URL.
• Attribute Format for "to" Parameter: The format for the "to" parameter in the URL would depend on how ISVG stores the phone number of the user. You would need to identify the attribute that holds the user's phone number and replace msisdn in the URL with that attribute's value. It could be something like [user.phone] or [user.mobile] depending on ISVG's attribute naming.
• Attribute Format for "text" Parameter: Similar to the "to" parameter, you need to identify the attribute in ISVG where the SMS content is stored. If you have a notification template or an attribute that holds the SMS body, replace [sms_content] with that attribute's value, such as [notification.sms_body].

It's important to understand how ISVG structures and stores user data and notification content. You might need to refer to ISVG's documentation or consult their support to determine the exact attribute names and placeholders for your use case.

Please note that dealing with sensitive information like usernames and passwords in URLs can be a security risk. Ensure that your setup follows best practices for secure transmission of sensitive data, such as using HTTPS, proper encryption, and adhering to any security guidelines provided by your SMS gateway provider.

------------------------------
Max Harry
------------------------------