[midPoint] Fwd: SMS Notification
Jason Everling
jeverling at bshp.edu
Tue Feb 28 15:08:01 CET 2017
I have never used anything outside of what I posted, but in a standard
notification you add the parts, you could try,
+ requestee?.getName()?.getOrig() which is the username and +
midpoint.getPlaintextUserPassword(requestee) is the password of the account
being changed.
Within our notification I get the username and password with +
encodedMessageText , it displays the below. Can you post what you get from
the sms-notifications log
'Password for user tauser2 is: n3wPassw0rd'
JASON
On Tue, Feb 28, 2017 at 12:26 AM, mceylan <mrveceylan at gmail.com> wrote:
> Hi Gustav, I enter real information in the live system. I did not want to
> write Mail. Because, gateway real username and password.
>
> There is no problem sending SMS. The problem is to send the username and
> password of the user I created in sms and to inform when the account is
> changed
>
>
> Thanks,
>
>
> 2017-02-28 7:58 GMT+02:00 Pálos Gustáv <gustav.palos at evolveum.com>:
>
>> Hi Merve,
>>
>> username and password are not variables, are you REAL username and REAL
>> password, please replace it like this:
>> http:/my-gateway/api/v3/sendsms/plain?user=palos&passwor
>> d=abcd123X&sender=XX....
>>
>> Gustav
>>
>>
>> 2017-02-28 6:49 GMT+01:00 mceylan <mrveceylan at gmail.com>:
>>
>>> Hi Jason,
>>>
>>> The message I wrote in EncodedMessageText comes up but the username and
>>> password do not come up. How can I send those variables in the script
>>>
>>>
>>> <handler>
>>> <userPasswordNotifier>
>>> <recipientExpression>
>>> <script>
>>> <code>requestee.getTelephoneNumber()</code>
>>> </script>
>>> </recipientExpression>
>>> <transport>sms</transport>
>>> </userPasswordNotifier>
>>> </handler>
>>> <sms>
>>> <gateway>
>>> <url>
>>> <script>
>>> <code>"http:/my-gateway/api/v3
>>> /sendsms/plain?user=username&password=password&sender=XX" +
>>> "&GSM=" + to + "&text=" + "account"</code>
>>> </script>
>>> </url>
>>> </gateway>
>>> </sms>
>>>
>>>
>>> log
>>>
>>>
>>> send to message "account"
>>>
>>> Thanks,
>>>
>>> 2017-02-28 2:28 GMT+02:00 Jason Everling <jeverling at bshp.edu>:
>>>
>>>> If you are testing SMS then yes, use a test account with your phone
>>>> number.
>>>>
>>>> JASON
>>>>
>>>> On Mon, Feb 27, 2017 at 1:57 AM, mceylan <mrveceylan at gmail.com> wrote:
>>>>
>>>>> thanks Jason, no problem. There will be another responsibility.
>>>>>
>>>>>
>>>>> For changes made to specific users' accounts, SMS will be provided to
>>>>> the user. Do I submit changes to my account? Can I also send a username
>>>>> and password?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> 2017-02-23 17:28 GMT+02:00 Jason Everling <jeverling at bshp.edu>:
>>>>>
>>>>>> Maybe try the below, your sms code has changed a few times between
>>>>>> your messages, GSM= I am assuming is the phone number to send
>>>>>>
>>>>>> <notificationConfiguration>
>>>>>> <handler>
>>>>>> <userPasswordNotifier>
>>>>>> <recipientExpression>
>>>>>> <script>
>>>>>> <code>
>>>>>> requestee.getTelephoneNumber()
>>>>>> </code>
>>>>>> </script>
>>>>>> </recipientExpression>
>>>>>> <transport>sms</transport>
>>>>>> </userPasswordNotifier>
>>>>>> </handler>
>>>>>> <sms>
>>>>>> <gateway>
>>>>>> <url>
>>>>>> <script>
>>>>>> <code>"http://my-gateway/api/v3/sendsms/plain?user=USERNAME&
>>>>>> amp;password=PASSWORD&SMSText=" + encodedMessageText +
>>>>>> "&GSM=" + to</code>
>>>>>> </script>
>>>>>> </url>
>>>>>> </gateway>
>>>>>> </sms>
>>>>>>
>>>>>> JASON
>>>>>>
>>>>>> On Thu, Feb 23, 2017 at 9:06 AM, Jason Everling <jeverling at bshp.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> I don't see a part in your gateway code that contains the 'to' field
>>>>>>> , how does it know which phone to send the message to?
>>>>>>>
>>>>>>> Some where in there you should have + to and also +
>>>>>>> encodedMessageText
>>>>>>>
>>>>>>> The 'to' variable is what requestee.getTelephoneNumber() returns
>>>>>>> and encodedMessageText variable returns the message, password in
>>>>>>> the case of userPasswordNotifier, which mine sends by default,
>>>>>>>
>>>>>>> '================ Wed Feb 22 08:43:21 CST 2017 =======
>>>>>>> Message{to='[12107654321 <(210)%20765-4321>]', subject='User
>>>>>>> password notification', contentType='null', body='Password for user tauser2
>>>>>>> is: s0m3passW0rd'}
>>>>>>> '
>>>>>>>
>>>>>>>
>>>>>>> Somewhere in this url you have to have the 'to' variable, don't know
>>>>>>> which gateway you are using so I cant tell you how it is used and where to
>>>>>>> insert it,
>>>>>>>
>>>>>>> "http://my-gateway/api/v3/sendsms/plain?user=USERNAME&pa
>>>>>>> ssword=PASSWORD&sender=SIFRE&SMSText=test123&" +
>>>>>>> "&text=" + "deneme"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> midPoint mailing list
>>>>>> midPoint at lists.evolveum.com
>>>>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Merve CEYLAN
>>>>>
>>>>> _______________________________________________
>>>>> midPoint mailing list
>>>>> midPoint at lists.evolveum.com
>>>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> midPoint mailing list
>>>> midPoint at lists.evolveum.com
>>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>>
>>>>
>>>
>>>
>>> --
>>> Merve CEYLAN
>>>
>>> _______________________________________________
>>> midPoint mailing list
>>> midPoint at lists.evolveum.com
>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>>
>>>
>>
>>
>> --
>> s pozdravom
>>
>> Gustáv Pálos
>>
>>
>>
>> --
>> Gustáv Pálos
>> Identity Engineer
>> evolveum.com
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>
>>
>
>
> --
> Merve CEYLAN
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170228/fd6d7426/attachment.htm>
More information about the midPoint
mailing list