Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2399

The template macro for $resetlink isn't picked up on API generated users

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Medium
    • None
    • 2.1.1
    • Integration/Connectors
    • None
    • Win 2008 R2 server
      MS sql 2008

    Description

      Scenario:

      1. A user is created using the API
      2. The user's password i reset using the API
      3. The e-mail sent to the user looks like below:

      Hello testuser1 testuser1,
      
      You (or someone else) have requested to reset your password for OSMcrowd on Tue Apr 12 10:45:30 CEST 2011.
      
      If you follow the link below you will be able to personally reset your password.
      $resetlink
      
      This password reset request is valid for the next 24 hours.
      
      Here are the details of your account:
      
      Username: testuser1
      Full Name: testuser1 testuser1
      
      OSMcrowd Administrator
      

      As you can see, the resetlink is not set.
      However - doing the same using the web interface is OK:

      My customer is currently integrating Crowd into their own applications. Most likely it will handle approximately 7-10 000 users in the coming years if implemented as suggested. The function with reset password using the API is important to us as we cannot tell the user himself to go to this address and do this and this. So this function is quite important to us. It is not more than a 'major' at the current time, but it can become 'critical' if this is not solved for the coming months. Simply because no-fix means that we most likely cannot use the system as we want.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              39ec62ae228f Ivar
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: